9 ms·
Still know a heck of a lot of people using it. Even know one researcher using it for a new project. It will be decades before the final Python 2 program goes o
by MattGaiser 7y ago
Still know a heck of a lot of people using it. Even know one researcher using it for a new project.
It will be decades before the final Python 2 program goes offline.
- deleted 7y ago[deleted]
- smitty1e 7y ago"So?" said COBOL.
- mullen 7y ago"Hold my beer!" - COBOL
- Izkata 7y agoJust discovered a week or two ago a pretty important part of one of our internal systems is running on python 2.6
- loeg 7y agoCaveat about 2.7: HTTPS switches from default-non-validating to default-validating. If your internal system uses SSL, and you have a bunch of self-signed certs, for example.
- Izkata 7y agoI think we're prooobably good there, this system is primarily slinging around and transforming data between databases. The far bigger worry would be unexpected encoding issues corrupting the data when going from 2->3.
- downerending 7y agoThere's a lot of code out there that's important, but not worth porting to a new language (which Python 3 is).
- acdha 7y agoI think describing it as porting to a new language is misleading: on most of my projects, most of the work is a few minutes — run modernize/futurize, check the tests, etc. If the original developers were really sloppy about how they handle encoding, it can take longer but most of the problems I've seen have very little to do with Python rather than the fact that something still running Python 2 likely has significant technical debt issues — especially things like not having test coverage which make it a lot harder to ship changes.
- downerending 7y ago> likely has significant technical debt issues You're not wrong, but as a practical matter, that pretty much describes our entire industry.
- acdha 7y agoCompletely agreed — I would just argue that the “Python 2 vs. 3” argument is a distraction. Java hasn't had as breaking a change but there are still a ton of places running Java 6 or 7 because they like skimping on developers more than getting security updates.
- Joeboy 7y agoOur product took about a year to port, from getting the go-ahead to the eventual production switch. Running modernize / futurize was like 0.01% of the work. You're right though, we're fighting our way out of technical debt and switching to python 3 was absolutely necessary. It's forced us to sort out a lot of sketchy string / bytes handling. We do, mercifully, have ~90% test coverage.
- abiogenesis 7y agoA year is astronomical. Does it involve writing tests that did not exist before?
- 7y ago
- zitterbewegung 7y agoThere isn’t anything inherently wrong with still using 2.7.x . Just don’t expect updates. For new code using 3.7 is probably the best bet at this time.
- deleted 7y ago[deleted]
- azinman2 7y agoI thought there won't be any more security updates?
- NikolaeVarius 7y agoSo? Im sure my non internet facing scripts care
- acdha 7y agoRed Hat, Ubuntu, etc. are going to support Python 2 for the duration of the operating system releases which shipped it. I would assume that Anaconda, et al. will have similar options for paid customers.
- DCKing 7y agoRed Hat has committed to keeping Python 2 on life support until 2024 as part of Red Hat Enterprise Linux 8 [1] so you can get security fixes for Python 2 until then if you use CentOS 8. Canonical will not provide long term support for Python 2 as part of Ubuntu 20.04 LTS. In Ubuntu 20.04, Python 2 is a "universe" package [2] that does not receive updates by Canonical. This means that the you will only get Python 2 security update guarantees with Ubuntu is on 18.04 LTS until April 2023. Debian is making an active effort [3] to remove Python 2 and packages that depend on it for its next release. It'll likely support Python 2 as part of Debian Buster until 2024. Note that if you're reading this to delay your move to Python 3 by another few years, you're doing it wrong. This list shows even all slow enterprise-y distros have a deadline for Python 2, not that you can stretch your stuff for a couple of more years :) [1]: https://access.redhat.com/solutions/4455511 https://access.redhat.com/solutions/4455511 [2]: https://packages.ubuntu.com/focal/python2 https://packages.ubuntu.com/focal/python2 [3]: https://wiki.debian.org/Python/2Removal https://wiki.debian.org/Python/2Removal
- deleted 7y ago[deleted]
- colanderman 7y agoYa, there's no way this is the "final" release. Maybe by the core Python team, but it will be forked to fix bugs. Ten years from now there will still be Python 2 code running critical infrastructure at various companies, and the most responsible path to address discovered issues in the runtime will not be "rewrite the application to work in Python 3!" but "upgrade the interpreter to this community-vetted fork of 2.7.18". Mumble mumble something about conflating languages with implementations.
- tom_mellior 7y ago> Mumble mumble something about conflating languages with implementations. So your claim is that "Python 2" is a language spec, not an implementation? And that there will be future releases of this language spec in the future? I doubt it. I agree it's likely that there will be people wasting their time maintaining an interpreter fork, but that will not be Python-the-language (a trademarked term BTW), it will be a fork of the implementation.
- colanderman 7y agoNo, my claim is that, while ceasing development of the language Python 2 is wholly sensible, ceasing development of the implementation Python 2 (CPython specifically) is not (due the almost certain existence of latent bugs). My "mumble" at the end was meant exactly in reference to that. I suppose one could argue that, the CPython implementation is the language specification. (And I seem to recall hearing that notion somewhere years ago.) In which case, it would not be possible to freeze development of the language without freezing the implementation as well. There are various reasons I wholeheartedly disagree with such a characterization, but I guess there's some self-consistency there at least.
- nxpnsv 7y agoThis is clear, but does the cpython team want to maintain Python2? If not, either it’s time to use an alternative or move on....
- tom_mellior 7y ago
- contravariant 7y agoDoes anyone know what the main reason is for not updating from python 2? I'm genuinely curious as I don't really know any modules that won't work under Python 3 and I can't really come up with any other blocking changes that would make upgrading that hard.
- TylerE 7y agoBecause giant codebase that would take effort++++ to do so for no perceived gain, with possible addition of new bugs.
- mywittyname 7y ago> effort++++ effort += 1 + 1 Ported to Python3 for you.
- imtringued 7y agoThat's how we get decades old cobol codebases that nobody understands.
- jefft255 7y agoLot’s of code is simply unmaintained. The guy that wrote it is gone, it’s still running fine so nobody is touching it. Businesses don’t want to take the risk and spend the money to upgrade it. Maybe you don’t realize the insane amount of code that is in this state!!
- BeetleB 7y ago> Even know one researcher using it for a new project. Knowing researchers (at least in academia), they're the last people I would expect to change.
- takeda 7y agoAnd those are least worrying, once they publish their thesis, they don't give a damn about their code anymore and it just dies natural death ;)