Python 2 Woes
I started using pipenv a while back, and
I think it represents a genuine positive step in Python dependency resolution.
Command line usage feels very similar to using npm (in my mind the epitome of
a good package manager), which is a breath of fresh air if you’re used to using
virtualenv and pip independently.
In my job I work on a number of Python2 projects, so I’ve found myself using the following command to initialize pipenv in a project folder:
me@local:~/path/to/project$ pipenv --python 2
Every time I do this I’m reminded of this site.
Python 2 is on the way out. Out with stupid logging, UnicodeDecodeErrors
two string types (unicode and str), and integer division!