25 ms·
In 2015, there was no way I could have moved to Python 3. There were too many libraries I depended on that hadn't ported yet. In 2019, I feel pretty confident
by jedberg 7y ago
In 2015, there was no way I could have moved to Python 3. There were too many libraries I depended on that hadn't ported yet.
In 2019, I feel pretty confident about using Python 3, having used it exclusively for about 18 months now.
For my personal use case at least, this timeline worked out well for me. Hopefully it works out for most everyone. I can't imagine they made this decision without at least some data backing it up.
- spurdoman77 7y agoPersonal use can be quite different to business use cases. For many companies the conversion can be quite horrific, they might be quite happy to pay for support for older versions.
- reitzensteinm 7y agoBased on your timeline, a four year gap from "not yet ready to migrate" to "we won't fix security vulnerabilities" is very short. Python is an open source project I've used and contributed nothing to, so I don't have the right to be a back seat driver. Were it a commercial project and I was a customer, I would be quite upset.
- PeterisP 7y agoThe thing is, a four year gap is very large from the perspective of "should we drop everything else and prioritize porting our library to python3 right now". If the deadline wasn't 2020 but 2024, then you wouldn't get more time, simply we'd be at "not yet ready to migrate" state right now, as major libraries would not have switched yet.
- hobofan 7y ago> porting our library Library, as is most open source libraries out there, sure. For a big company-internal Python codebase that also has to wait for all the major libraries to migrate first, that time frame can quickly shrink to 1-2 years, which is very little.
- PeterisP 7y agoYou're waiting for other people to do stuff, and for many of them 1-2 years is the timeframe when they are likely to start working on it. From that perspective 1-2 years is not "too short", it's the "we intentionally chose this as the optimal time". That doesn't really depend on when the deadline is; if you postpone the deadline, then they postpone the migration - as pretty much every library did back in 2014 when the deadline was postponed by 5(!) years. Beggars can't be choosers; if your company wants or needs major libraries to have migrated 4-5 years before the deadline, then your company has to participate in making that migration happen. Or accept that it's going to be done later than you'd like, because the needs and motivation of these library maintainers are quite different from the motivation of Python core maintainers.
- braythwayt 7y agoThis x 1000. “The free libraries we chose to depend upon haven’t migrated.” Do you have programmers? “Of course.” Put them to work. “We have other priorities.” Well then. Your choice, your outcome.
- marcus_holmes 7y agoThis attitude is ridiculous. I'm supposed to go and tell all the various projects that I depend on that they have to change their upgrade timescales to suit mine? Even if I had enough time to help them all meet that kind of timescale, why would they agree to fit their changes into my required deadline? Maintainers are under a lot of pressure. Having users come along and say "we'll add 50 developers to your project if you agree to ship v3 compliance by next month" is not reducing that pressure, it's adding to it. More programmers != better results or faster delivery. Your solution is just going to create more problems.
- jedberg 7y ago> Based on your timeline, a four year gap from "not yet ready to migrate" to "we won't fix security vulnerabilities" is very short. Is it though? Especially since as late as 2014, everyone was under the assumption that in 2015 security support would end. We were already trying to migrate long before that. The five year extension seems pretty reasonable to me.
- Ensorceled 7y agoIn 2014, things were not quite ready so they extended it 6 more years. If you were upset by this you really need to get out of software development.
- shakna 7y agoPython 2's EOL was first announced in 2008, it was extended in 2014. That's more than a decade of forewarning that this was coming down the line. A decade of Python2 receiving security fixes. Were I a commercial customer, and had been told to switch to the new version ten years ago, then it's on me if I still have started the migration yet.
- mantap 7y agoYou couldn't switch to Python 3 until the middle part of this decade unless the stars aligned with your dependencies, the library support wasn't there. And the first releases of Python 3 were glorified betas, the first "usable" version of Python 3 is often considered to be version 3.3 released in 2012.
- ensignavenger 7y agoBut you could easily write Python 3 compatible code so that upgrading once your dependacies were ready was easy. You also could have contributed to your dependancies to help them become Python 3 compatible.
- mehrdadn 7y ago> But you could easily write Python 3 compatible code so that upgrading once your dependacies were ready was easy. This sounds a bit like telling someone, oh, you could've easily started driving an EV, so that once charging stations were actually out there, you'd have been ready...
- ericvsmith 7y ago> This sounds a bit like telling someone, oh, you could've easily started driving an EV, so that once charging stations were actually out there, you'd have been ready... While car analogies are notoriously bad, it's much more like "I'm going to buy a plug-in hybrid and use gasoline until charging stations are widely available". You can write code that works in Python 2 that takes zero effort to run in Python 3. I (and many others) have been doing this for years. Just look at the number of packages on PyPI that run, unmodified, on 2 and 3. [Edit: gas -> gasoline]
- MR4D 7y agoIt was longer than Apple’s move to 64 bit apps on the iPhone. Actually, depending on what action you pin dates to, it was twice as long. One other thing - you can’t run non-64 bit apps anymore. You can still run Python 2.
- Wowfunhappy 7y agoThat's a pretty low bar. I still think that move by Apple was pretty terrible. Especially given that it's 100% impossible to downgrade iOS (your last point).
- scarface74 7y agoAnd it’s entirely impossible to run 32 bit apps on newer Apple ARM chips. There is always a cost to keeping old APIs or in Apple’s case, old silicon.
- maccard 7y agoIt's actually longer than android has been alive...
- appleflaxen 7y agoBut it's not commercial, and you had four years of guidance. I feel like this the python community has been the epitome of class regarding communication during a transition.
- logifail 7y agoWindows 10 Enterprise LTSB 2015 (the original long term support version of Windows 10 Enterprise) doesn't support installing .Net 4.7 at all. There are an increasing number of applications which require .Net 4.7, we found one early this year. Promising "10 years of support" for a product is great, but if/when other vendors decide to undercut this, you can still be SoL :(
- hiccuphippo 7y agoI'm pretty sure there will be more than one commercial offer for Python2 support in the future.
- johannes1234321 7y ago> I can't imagine they made this decision without at least some data backing it up. Mind that there is a feedback loop between data of current usage and an eol announcement. If they announce an EOL close by this creates pressure to migrate.
- bigiain 7y agoIn my mind, I kinda hope that data they used to back this decision up was asking "Hey, all you other volunteer Python language devs? How many of you want to work on the old Python2 codebase still? How many of you would prefer to be working on Python3? OK, that's just about unanimous. How about we all get drunk on Newyears and shut it down on Jan 1st?" You can still get Microsoft Windows XP support today. If you're prepared to pay enough. I wonder how many of the people who're upset by this have ever or ever worked for companies that've ever sent anything more than pocket change to the people Python?
- decoyworker 7y ago>In 2015, there was no way I could have moved to Python 3. There were too many libraries I depended on that hadn't ported yet. You could work on porting them or be part of that effort?
- normalhuman 7y ago> For my personal use case at least, this timeline worked out well for me. Hint for Hacker News commenters: 99% of the time, if your phrase includes the term "use case", you can safely just delete it and lose no meaning. It's just a way to say "for me" or "for them" that sounds more technical but really isn't. In this case, you could say "This timeline worked out well for me".
- cheez 7y agoAre you sure you are indeed a normal human?
- deleted 7y ago[deleted]
- fortydegrees 7y agoSame with 'utilize' -> 'use'
- teekert 7y agoAnd 'A.I.' -> 'Algorithm'
- cheez 7y ago'A.I' -> 'Linear regression' * ducks and runs
- partialrecall 7y agoIt's not restricted to tech. Cops do it too: "This particular individual" -> "this person"
- ben509 7y agoI've heard "orientate" for "orient" quite a few times, though maybe it was occidental.
- bradenb 7y ago
- ueiuestu 7y agoThis makes me wonder, are there any software frameworks and languages that are specifically built for multi decade use? Where they only release security updates and no breaking changes?
- koreth1 7y agoI would have said Java, but then they decided to shove modules down everyone's throat.
- Crinus 7y agoWouldn't Java 1.0 code still work in Java $LATEST even with modules? As i understand it the question was about keeping stuff working, not refusing to add new stuff.
- jerven 7y ago1.1 is what would still work. There was not much Java 1 code in existence. Java 1.4 to 5 was annoying and the last release to introduce a lot of source code in compatibility. Which was sometime in 2004. Modules is mostly figuring out what switches to set on startup, not so much refuses to work.
- chrshawkes 7y agoI would say the Perl but then the Perl 6 fiasco made Python 3 look like a model citizen for upgrading code.
- mirchibajji 7y agoPerl5 is not being EOL'ed in favour of Perl6. When the time does come around for Perl5, I would guess that only a small fraction would migrate to Perl6.
- toyg 7y ago"Built for", probably not. "That guarantees support for", some Windows releases and Microsoft stacks ended up doing more or less that, be it by accident or strategy. Probably some mainframe-related stuff too, being the only sort of thing around before the late '80s and possibly still in use. There is also the case of Oracle, which defines support as "you can read our knowledge base and we will answer a phone before telling you it can't be done", meaning their support is literally for life (of the company). And they still manage to screw it up by deleting old KM articles... Everything else in IT goes towards shorter and shorter support windows, because the field is always in flux and change (or rather churn) accelerates every year.