Python 2.7 EOL plans (Leaving feedback is encouraged)
See original GitHub issueIn a little over a month, the PSF will end support for Python 2. @fcurella, what do you intend to do with this project concerning Python 2 EOL? Do you plan to retain support for a certain duration after the EOL date?
In any case, I can help with making everything Python 3 only, but I think Faker
should have at least one last “semi-significant”, if not significant, release that is Python 2 compatible for the poor souls who are stuck with Python 2. Your thoughts?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Python 2.7 EOL FAQ
Python 2 is only supported on Heroku's oldest stack, Heroku-18, which is deprecated and reaches end-of-life on April 30th, 2023.
Read more >Python 2 EOL - Now What?
for Python 2, the core development team will no longer support, update or provide new versions of Python 2 as of January 1,...
Read more >Where is Python 2 still used?
Python 2 is no longer supported, so there are no security patches to the language, runtime, and third party packages are dropping support...
Read more >Chapter 1. Python Versions
The end-of-life for Python 2.7.x is 2020, and no new features will be ... good for companies and projects to start think of...
Read more >Changelog - pip documentation v22.3.1
The Python 2 end of life warning now only shows on CPython, which is the implementation that has announced end of life plans....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So far, this is the plan:
six
etc.)Once python 2 is EOL, I would like to tag one last release supporting it and release a new major one dropping support altogether. People stuck on 2.x can just pin to the last supported version (ie `pip install Faker<4").
I don’t see the point into staying py2 compatible any longer than that. People already had plenty of time to upgrade. If they didn’t, it’s because something critical is preventing them from doing it, and prolonging Faker’s upgrade is unlikely to change that.
I appreciate any feedback, I’d like for this to be conversation with Faker’s users.
On Mon, Nov 25, 2019 at 8:11 AM malefice notifications@github.com wrote: