4 ms·
Any specific reason to develop this for Python 2 rather than Python 3?
by yoz-y 9y ago
Any specific reason to develop this for Python 2 rather than Python 3?
- melling 9y agoThe end of life is in 2020 but it doesn’t say when. Is this still the latest? http://legacy.python.org/dev/peps/pep-0373/ http://legacy.python.org/dev/peps/pep-0373/
- sanxiyn 9y agoIt's January 1st, 2020. https://mail.python.org/pipermail/python-dev/2018-March/152348.html https://mail.python.org/pipermail/python-dev/2018-March/1523...
- meddlepal 9y agoThere's still a lot of existing and new Python 2 code being written. Idealistically we would all be on Python 3, but software is a messy land.
- goatlover 9y agoIt's been ten years, so it's gone beyond "idealistically".
- CJefferson 9y agoStill not distributed by default on Mac or Ubuntu long term release, unlike 2.
- rspeer 9y agoThe current Ubuntu long-term support release is Xenial, which comes with only Python 3 installed. If you're talking about Trusty, its support is ending fairly soon. On Xenial, you have to separately install an optional package for Python 2. When you try to run /usr/bin/python on a fresh Xenial install, it'll tell you that you need to install a package such as python-minimal==2.7.11, whereas /usr/bin/python3 is already there.
- CJefferson 9y agoWoops, my LTS is obviously out of date. Thanks.
- Silhouette 9y agoIt hasn't been anything close to that long since major libraries mostly worked on 3, though. You can't just declare the old version of a major software ecosystem dead because you updated one part of it. We've seen it with operating systems, we've seen it with browsers, and we also see it with programming languages and all the libraries and tools that make them useful.
- BerislavLopac 9y agoIt has not been ten years, as only Python 3.6 and later is considered finalised.