Sunsetting Python2
See original GitHub issueI just wrote some code, and got bitten by the fact that it wasn’t supported by python2 (along the lines of a, *b = [1, 2, 3]
). The advanced unpacking features in python3 are incredibly useful for code like this, but can’t be used due to the current need to maintain python2 support. Would it be possible to get rid of python2 support soon?
I’d love to force everyone to use python3.6 (released December 2016), but I realize that may be a bit overzealous. However, forcing at least python3.5 (released September 2015) would allow additional unpacking generalizations (e.g. a, *b, c = [1, 2, 3, 4]
). Wikipedia has a list of release dates for those interested.
Thoughts?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Sunsetting Python 2
We are volunteers who make and take care of the Python programming language. We have decided that January 1, 2020, was the day...
Read more >Sunsetting Python 2 support
The developers of the Python language extended support of Python 2.7 from 2015 to January 1, 2020, recognising that many people were still...
Read more >Extended Support Past Python 2 EOL - ActiveState
The Python Software Foundation sunset Python 2 on January 1, 2020. End of Life (EOL) means there are no more official updates or...
Read more >How to Secure Python 2 Past End of Life (EOL) with ActiveState
Many dates were announced by the PSF to sunset Python 2 in favor of Python 3, notably in 2015 and 2020. But the...
Read more >Sunsetting Python 2 - Hacker News
(Unless your manager makes drive-by commits of py2-only code, months after you all agreed that all new code should be py3-compatible, and then ......
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 Free
Top 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
My $0.02 - I think it’s an okay idea, but cclib should really set out a specific timeframe (e.g., end of 2018) and substantially change the version number (e.g., cclib-2.x will only work with Py3).
While there’s a strong change towards Python3 in the entire science “stack,” the deadline is usually more like 2019-2020: http://python3statement.org
As per dev discussion, we will be dropping Py2 for v1.7 - separately from QCElemental and other changes that could be related.