Python2 was EOL'ed earlier this year and thus it may be worth considering dropping support for python2. Ideally this would reduce the complexity of the project making it easier to manage, test and release.
Pros:
Cons:
Note: Initially, this was suggested in #3369 under https://github.com/pypa/pipenv/issues/3369#issuecomment-630557465 as it appears that a python2 / cross support issue delayed the 2020 release. I've moved the discussion for dropping python2 here as to avoid further polluting the original ticket.
This is definitely something we could consider; I suspect we will look to coincide with pip dropping support which I believe is still a few months away. Once we do drop python 2 support we should be able to make some substantial gains in terms of performance and cleanup, so I think we are all excited.
I suspect we will look to coincide with pip dropping support which I believe is still a few months away.
Pip 20.3 (October 2020) will be the last version to support Python 2.7, and pip 21.0 (January 2021) will be the first version to drop it.
Also we could consider dropping Python 3.4.
Before dropping there should be a simple command to switch from python2 printed out each time you run the tool under python2. For example:
Warning, you are running pipenv under python2, python2 support is to be dropped
Use python3 -m pipenv install pipenv to switch to use python3 (or whatever the command is)See for more details at https://github.com/pypa/pipenv/issues/4261
and at https://www.python.org/doc/sunset-python-2/
imagine a python environment manager that only supports some of your environments
this project is completely braindead
And what about Python 3.5? It has reached its EOL recently, and probably could also be dropped.
Sources:
Most helpful comment
Also we could consider dropping Python 3.4.