News for hackers. Stuff that matters.
Re:Sunsetting Python 2 by jedberg on Monday September 09, 2019 @05:01AM (#20916392)
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.

Re:Sunsetting Python 2 by reitzensteinm on Monday September 09, 2019 @05:27AM (#20916548)
Based 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.

Re:Sunsetting Python 2 by shakna on Monday September 09, 2019 @06:11AM (#20916763)
Python 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.

Re:Sunsetting Python 2 by mikepurvis on Monday September 09, 2019 @09:58AM (#20918191)
It's interesting seeing who the holdouts are, though. Less than a year ago, the CEO of Sentry (the crash reporter) locked a Github thread with essentially "we'll get there when we get there, sometime in or after 2020." But then, as late as 2016 their stance was pretty much that they would never migrate, so I suppose it's not surprising that they aren't super prepared for it:

https://github.com/getsentry/sentry/issues/8806#issuecomment...

https://github.com/getsentry/sentry/issues/1152#issuecomment...

I mean, even supervisord is migrated at this point, and it was a long-time laggard.

Re:Sunsetting Python 2 by bscphil on Monday September 09, 2019 @12:18PM (#20919528)
Calibre is another well known case, and they don't plan to migrate.

Actually, I can't wait to remove it from my hard drive on Jan 1, since it's one of the most poorly designed apps I've ever used. It's really not surprising at all that they're not able to migrate it, assuming the quality of the app is indicative of the quality of the code. I wouldn't be surprised if the same was true of a lot of applications that are refusing to migrate. (I'll probably have to find an alternative to ebook-convert, the command line tool that's the only part of Calibre I use, or maybe I'll rewrite it in Python 3 myself.)

Re:Sunsetting Python 2 by partialrecall on Monday September 09, 2019 @12:50PM (#20919854)
The only good part of calibre is the `ebook-convert` commandline tool that has a stupid-simple interface (polar opposite of the gui) and handles all kinds of formats that pandoc doesn't.

The gui, Calibre proper, is a total nightmare. Functional, but my god is it esoteric and ugly. I've heard people actually use that gui as their primary ebook reading software and I just can't fathom how they find that tolerable.

https://manual.calibre-ebook.com/generated/en/ebook-convert....

Re:Sunsetting Python 2 by shscs911 on Monday September 09, 2019 @01:13PM (#20920053)
I dislike Calibre main GUI as well. It looks a bit dated and all, but really convenient for downloading books from Userfiction forums like Spacebattles via the Fanficfare plugin. Also good for simple editing of ebook metadata. Built-in ebook-viewer is highly configurable with custom keybindings and themable with custom CSS.This is my setup

https://imgur.com/a/nlAAlZn

Re:Sunsetting Python 2 by notthemessiah on Monday September 09, 2019 @01:15PM (#20920079)
I use Calibre as my primary e-book reader. I don't see many alternatives on Linux.
Re:Sunsetting Python 2 by shscs911 on Monday September 09, 2019 @01:27PM (#20920231)
I basically use Calibre ebook viewer for its configurability and customization. If you want a good ebook reader, give Foliate (https://github.com/johnfactotum/foliate) a try. That and Bookworm (https://github.com/babluboy/bookworm) are the best standalone ebook readers I've seen in Linux.
Re:Sunsetting Python 2 by michaelmrose on Tuesday September 10, 2019 @02:23AM (#20925565)
Other than having a simpler layout I don't really see either as better than calibres reader. What's better other than looks?
Re:Sunsetting Python 2 by shscs911 on Monday September 09, 2019 @12:49PM (#20919837)
Re:Sunsetting Python 2 by bscphil on Monday September 09, 2019 @02:05PM (#20920652)
If that's the case, I'm glad to see things are changing. Up until very recently, there seem to have been no plans to switch: https://bugs.launchpad.net/calibre/+bug/1714107

> No, it doesn't [need to convert to Python 3]. I am perfectly capable of maintaining python 2 myself. Far less work than migrating the entire calibre codebase.

Re:Sunsetting Python 2 by gnulinux on Tuesday September 10, 2019 @11:53AM (#20929581)
> I am perfectly capable of maintaining python 2 myself.

That's a very strange quote. I want to have this much self-confidence.

Re:Sunsetting Python 2 by dralley on Monday September 09, 2019 @03:51PM (#20921736)
Calibre is, in fact, migrating. There are at this point dozens of commits over the past few months to that goal. Not sure what changed his mind.
Re:Sunsetting Python 2 by iamnotacrook on Tuesday September 10, 2019 @01:35PM (#20930853)
Reality? You can maintain an absurd, unintuitive, dated UI by yourself fairly easily, but even someone who pushes out two minor updates per week is going to be taking on a little too much in my opinion if they believe they can also support a fork of a major language.
Re:Sunsetting Python 2 by tapia on Monday September 09, 2019 @12:38PM (#20919722)
And make a gnome core app with GTK3? That would pretty cool :)
Re:Sunsetting Python 2 by mynameisvlad on Monday September 09, 2019 @10:13PM (#20924535)
His responses leave an incredibly sour taste in my mouth. Not only is he obviously short sighted with his "Python 2 is not the past and Python 3 is not the future" but all his responses just sound like someone who got up on the wrong side of the bed. Every morning.
Re:Sunsetting Python 2 by mantap on Monday September 09, 2019 @06:58AM (#20916990)
You 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.
Re:Sunsetting Python 2 by ensignavenger on Monday September 09, 2019 @07:34AM (#20917160)
But 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.
Re:Sunsetting Python 2 by pfranz on Monday September 09, 2019 @01:58PM (#20920578)
I often hear this, but I just don't see this working in practice. A very similar example I have experience with, I've often worked with people who tried to write code that would be "compatible with Windows" (I primary work in a Linux environment). It makes the code more difficult to read and as soon as you try and run it in Windows it fails spectacularly.

You can write code that's compatible with both Python 2 and 3, but I don't think you can expect to be using Python 2 exclusively and write code that works well in Python 3 unless you're constantly running it with Python 3. Especially, if you don't have much firsthand Python 3 experience. This is much easier if your code is isolated from those dependencies and you write tests that run in both Python 2 and 3, but that's quite a bit more of a commitment than you seem to be implying.

Re:Sunsetting Python 2 by ensignavenger on Monday September 09, 2019 @06:32PM (#20923205)
There are a ton of open source projects that have done python 2/3 simultaneously in practice.

I get your point though about not being able to run full integration tests due to dependencies. Still, if you were making a good effort to keep the code Python 3 compliant, it would make upgrading much easier.

Also, my other suggestion- contributing to Python 3 compatibility for modules you depend on! That will give you Python 3 experience :)

Re:Sunsetting Python 2 by mikepurvis on Monday September 09, 2019 @09:45AM (#20918066)
Quick: run a shell command, split up the reply by line, run a regex on each line, and save the results to a yaml file— now, does what you wrote work correctly on both Python 2.7 and Python 3.3+? Yeah that's what I thought.

It's still hard to get bilingual Python correct today, and it was considerably harder before 3.3.

Re:Sunsetting Python 2 by radus on Monday September 09, 2019 @02:50PM (#20921068)
Okay, I did it.

    import subprocess
    import re
    import yaml

    output = subprocess.check_output(['ls', '-l'], universal_newlines=True)
    matching_lines = []

    for line in output.splitlines():
        if re.search(r'total', line):
            matching_lines.append(line)

    with open('matching_lines.yaml', 'w') as f:
        f.write(yaml.dump(matching_lines))
Python 3.7: https://repl.it/repls/PotableDamagedAutocad

Python 2.7: https://repl.it/repls/OrchidDirtyNotification

Re:Sunsetting Python 2 by mikepurvis on Monday September 09, 2019 @08:12PM (#20923924)
Nice. Yeah my life got a lot easier when I learned about `universal_newlines` changing the subprocess return type under Python 3.

The much worse case of this that I dealt with a few years ago was reading in and modifying XML files, and then saving the modified XML contents as strings in a yaml file (a keyed cache). The input XML files (which I didn't control) were not consistent about having the encoding marked, and that really made things a mess for ElementTree.

A taste: https://github.com/ros-infrastructure/rosdistro/search?q=utf...

Re:Sunsetting Python 2 by slavik81 on Tuesday September 10, 2019 @07:50AM (#20927180)
This program would crash with a UnicodeEncodeError upon encountering any file with a non-latin character in its name on Windows with Python 3.5 or earlier.

I know that's not the version of Python you were targeting, and I know you didn't write this program to be cross-platform, but I wrote a similar program and I was repeatedly surprised by those sorts of problems. I don't entirely agree with mikepurvis, but I do feel his pain.

Re:Sunsetting Python 2 by weberc2 on Monday September 09, 2019 @10:26AM (#20918477)
No one is arguing that upgrading would be trivial; the argument is that it's necessary work that could have been started 10 years ago. Also, if you run your unit tests on Python 2 and 3, you'll get pretty good pretty fast at writing 2-3 compatible code.
Re:Sunsetting Python 2 by mikepurvis on Monday September 09, 2019 @10:33AM (#20918549)
The comment I was specifically replying to asserted that "you could easily write Python 3 compatible code", and could have been doing so 10 years ago.

This is simply untrue— there are a dozen small stumbling blocks that mean that writing bilingual code has a real cost. And it's not as easy as just having the right CI setup, especially if it's ten years ago and most of your dependencies haven't migrated.

Re:Sunsetting Python 2 by weberc2 on Monday September 09, 2019 @10:50AM (#20918713)
Ah, I see the confusion. In this case, "easily" is relative. The assertion "you could easily write Python 3 compatible code" was in response to the (implied?) assertion "you can't do anything to migrate unless your dependencies are migrated". Perhaps "simply" would have been a better word choice than "easily". To your point, writing 2-3 compatible code has a real cost, but to the GP's point, it's the obvious solution to the "can't do anything until deps are migrated" problem.
Re:Sunsetting Python 2 by logifail on Monday September 09, 2019 @01:05PM (#20919977)
> To your point, writing 2-3 compatible code has a real cost, but to the GP's point, it's the obvious solution to the "can't do anything until deps are migrated" problem

Q: Ten years ago how would you have explained to your manager that you needed your team to start writing 2-3 compatible code, which obviously takes considerably more time and effort than sticking with 2 compatible code?

Re:Sunsetting Python 2 by joshuamorton on Monday September 09, 2019 @09:21PM (#20924285)
It doesn't take considerably more time.

At this point, all the code I write is 2/3 compatible, and the things that annoy me are all py3 only features. Backwards compatibility stuff is pretty easy. Most of the easy problems are easy, and six has solved all the hard ones for like 7 years.

And I've been writing some of my code 2/3 compatible since 3.4.

Re:Sunsetting Python 2 by mehrdadn on Monday September 09, 2019 @07:47AM (#20917230)
> 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...

Re:Sunsetting Python 2 by ericvsmith on Monday September 09, 2019 @07:58AM (#20917308)
> 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]

Re:Sunsetting Python 2 by mehrdadn on Monday September 09, 2019 @08:03AM (#20917334)
I try to write compatible code myself too, and the only reason it's "zero effort" to run in Python 3 is that I've already invested said effort when making it compatible. Getting strings and paths and stdio to be cross-compatible and working correctly in both 2 and 3 can be quite painful in my experience. Which was kind of my point with the vehicle analogy. It requires a significant investment that you're ignoring, and lack of enough underlying support to justify it during that time.
Re:Sunsetting Python 2 by weberc2 on Monday September 09, 2019 @10:31AM (#20918517)
Driving an EV without charging stations is (nearly) useless. You can still run Python 2-3 code with a Python 2 interpreter with no significant consequence.
Re:Sunsetting Python 2 by WorldMaker on Monday September 09, 2019 @04:57PM (#20922400)
EV drivers don't need charging stations at all if they have an open plug at home or at work. The metaphor still sort of works that Python developers had plenty of time where maybe they didn't have enough charging stations on the wide open highway roads of Production to use Python 3 there, but certainly could have been happy to use an EV to commute from home (hobby projects) to the work parking lot (side projects, automation projects, new projects) and back while they waited for those "charging stations" to be built.
Re:Sunsetting Python 2 by weberc2 on Monday September 09, 2019 @07:00PM (#20923431)
I don't want to debate the amount of shoehorning necessary to validate the metaphor. We all understand concretely the issue at hand, the metaphor is only obfuscating at this point.
Re:Sunsetting Python 2 by collinmanderson on Monday September 09, 2019 @10:13AM (#20918347)
I feel like there were 3 steps:

- 2008-2012 Python 3 becoming usable (byte formatting, six library)

- 2012-2016 Libraries (Django, etc) becoming compatible

- 2016-today Applications (Trac, Ansible, Chrome[1], etc) becoming compatible.

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=942720

Re:Sunsetting Python 2 by oblio on Monday September 09, 2019 @08:24AM (#20917439)
2012 was 7 years ago.
Re:Sunsetting Python 2 by your-nanny on Monday September 09, 2019 @04:31PM (#20922144)
well what if your best guess was that py2 would never actually be deprecated. Certainly in the early tens I had serious doubts.
Re:Sunsetting Python 2 by PeterisP on Monday September 09, 2019 @05:34AM (#20916591)
The 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.

Re:Sunsetting Python 2 by wwright on Monday September 09, 2019 @07:43AM (#20917194)
If the only way your organization can prioritize this is either “drop everything and update” or “completely ignore and do no work to prepare,” then it sounds like Python versioning is not your biggest problem.
Re:Sunsetting Python 2 by marcus_holmes on Monday September 09, 2019 @08:43AM (#20917565)
I get this, though: porting code affects all parts of the code base, so it generates git conflicts all the time. It's way more of a pain to do than routine feature development or refactors. It gets difficult to have part of the team work on features while another group works on the port to a new version, because that generates a ton of conflicts. It's easier to get the entire team working on the port.

I had to manage a mature codebase upgrading Ruby versions, and it was painful. And that is fairly mild by comparison; not the big jump from Python 2 to 3.

Re:Sunsetting Python 2 by shawxe on Monday September 09, 2019 @08:36AM (#20917517)
Unfortunately, I think this type of thing actually is the case for many organizations. Trying to explain the business case for paying off technical debt to a non-technical person can be very difficult when "right now everything works."
Re:Sunsetting Python 2 by cogman10 on Monday September 09, 2019 @08:49AM (#20917600)
I've had to fight developers over this.

A lot of devs like to not worry about new things.

Re:Sunsetting Python 2 by wwright on Tuesday September 10, 2019 @06:46AM (#20926808)
I can really understand that… but I believe that such organizations will experience significantly more problems than just Python upgrades. (I work for one.)
Re:Sunsetting Python 2 by hobofan on Monday September 09, 2019 @06:31AM (#20916872)
> 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.

Re:Sunsetting Python 2 by PeterisP on Monday September 09, 2019 @06:44AM (#20916923)
You'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.

Re:Sunsetting Python 2 by braythwayt on Monday September 09, 2019 @07:28AM (#20917136)
This 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.

Re:Sunsetting Python 2 by adamc on Monday September 09, 2019 @10:36AM (#20918572)
This is dumb. You're blaming people who probably don't get to call the shots. The managers who do have the ability to make different decisions are, themselves, often under the gun to meet other commitments.

Sure, they will have to cope. One of the ways people cope is by accepting security risks and continuing to run with old versions. Another is to decide that Python isn't for them, and move resources toward better platforms with commercial support for older code.

The fact is, that until a few years ago there were too many libraries that were not compatible for most organizations to make the switch. So, effectively the window for those organizations has only been a few years.

Re:Sunsetting Python 2 by nwallin on Monday September 09, 2019 @01:53PM (#20920532)
> You're blaming people who probably don't get to call the shots.

I think he's blaming organizations, not engineers.

I also think organizational dysfunction is a problem that isn't a technical problem that the Python project has the capability or duty to solve.

Re:Sunsetting Python 2 by dragonwriter on Monday September 09, 2019 @08:07PM (#20923889)
> You're blaming people who probably don't get to call the shots.

No one is doing that.

OTOH, it's not PSFs job to protect developers from bad management.

Re:Sunsetting Python 2 by paulmd on Tuesday September 10, 2019 @12:31PM (#20930004)
There is also the third choice - you don't migrate and keep doing your job (developing features) on the legacy code base. Things like certificates will have ad-hoc solutions pushed whether you like it or not, and the language will keep trundling along.

If there wind up being major security issues, there will be little choice but for someone to take up the mantle and fix them. Because companies aren't going to switch, and when you've got a botnet ravaging the internet they can't flip a switch and do a big-bang rewrite, someone will have to push out a patch for them.

This isn't the end of Python 2, it's just the Python team washing their hands of it. Ask PHP or Cobol users how their attempts to kill legacy codebases worked out for them.

This whole endeavor was complete folly from the Python foundation to begin with. A big-bang rewrite because they didn't like the syntax, and they didn't even fix the GIL while they were at it.

Re:Sunsetting Python 2 by marcus_holmes on Monday September 09, 2019 @08:49AM (#20917610)
This 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.

Re:Sunsetting Python 2 by ilikehurdles on Monday September 09, 2019 @09:45AM (#20918072)
You fork the library. You fix the incompatibility issues. You issue PRs back to the mainline to help them adopt the same fixes. At some point in the future you can switch back to the main repo if they've migrated, or you can consider that library abandoned and continue to maintain your own or find an alternate.

At no point do you have to wait on anyone else, you choose to.

Re:Sunsetting Python 2 by Kaiyou on Monday September 09, 2019 @11:03AM (#20918831)
You can do that, but then they won't accept your solution, so you just spend time developing a parallel system that you need to support yourself until the end of time. Been there, done that.
Re:Sunsetting Python 2 by ilikehurdles on Monday September 09, 2019 @11:39AM (#20919144)
If there is significant demand for solving the problem your fork solves, others will migrate to it. This is made harder when the main solution gets to squeak along for 10 extra years on a version of the language that should no longer get first-party support. Of course there is going to be less demand for that Py3 solution when there is no immediate consequence for continuing on Py2. Killing security update support for 2 will boost the demand for libraries using 3, and make it more likely that your fork gets merged or becomes the defacto standard.

The Python 2->3 window is an example of where being too nice to too many users harms the project. Once Python 2 is dead, people will choose between being the sole maintainer of a Python 3 fork of some Python 2 library versus a being a sole maintainer of their entire Python 2 stack from the language layer on up.

Re:Sunsetting Python 2 by Kaiyou on Wednesday September 11, 2019 @05:08AM (#20937938)
How are they supposed to migrate if I can't openly host my solution because it was developed on company time? Merging back into the original project is one thing, but making your solution available some other way is a whole other story.
Re:Sunsetting Python 2 by BeetleB on Monday September 09, 2019 @11:18AM (#20918956)
This is the reality of having lots of open source dependencies. Important changes/bugs may exist, and the maintainers are under no obligation to fix them to suit your business needs. If you want them fixed, you contribute to the code base (or fork it) and fix it.

Still better than my last programming job where the vendor of a vital piece of HW had provided a C++ API (also vital), but refused to provide dlls that would work in anything newer than VS2010. At least with open source you can do something about it.

Re:Sunsetting Python 2 by hobofan on Monday September 09, 2019 @09:06AM (#20917721)
You shouldn't take "Do you have programmers?" too literally.

Programmers ~= Resources ~= Money

=> If you want your dependencies to be upgraded in a reasonable time frame, try to contribute to financing the maintainers (or support them in a manner _they_ find suitable).

Re:Sunsetting Python 2 by SiempreViernes on Monday September 09, 2019 @06:46AM (#20916938)
The time frame is 12 years though, since the sunset was originally announced in 2008.
Re:Sunsetting Python 2 by hobofan on Monday September 09, 2019 @07:48AM (#20917235)
A lot of libraries refused to migrate before Python 3.5(?) came out which was ~4 years ago. IIRC earlier Python 3 versions had performance regressions compared to Python 2.
Re:Sunsetting Python 2 by adamc on Monday September 09, 2019 @10:39AM (#20918598)
This. For most organizations, the effective window has only been 2-3 years.

Personally, I would guess that many organizations will be running in Python 2 for at least parts of their codebase come 2020.

Re:Sunsetting Python 2 by jedberg on Monday September 09, 2019 @05:36AM (#20916600)
> 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.

Re:Sunsetting Python 2 by MR4D on Monday September 09, 2019 @06:19AM (#20916803)
It 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.

Re:Sunsetting Python 2 by Wowfunhappy on Monday September 09, 2019 @06:26AM (#20916842)
That'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).
Re:Sunsetting Python 2 by scarface74 on Monday September 09, 2019 @07:45AM (#20917211)
And 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.
Re:Sunsetting Python 2 by maccard on Monday September 09, 2019 @10:20AM (#20918415)
It's actually longer than android has been alive...
Re:Sunsetting Python 2 by appleflaxen on Monday September 09, 2019 @07:12AM (#20917065)
But 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.

Re:Sunsetting Python 2 by Ensorceled on Monday September 09, 2019 @05:50AM (#20916665)
In 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.
Re:Sunsetting Python 2 by logifail on Monday September 09, 2019 @12:48PM (#20919827)
Windows 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 :(

Re:Sunsetting Python 2 by hiccuphippo on Monday September 09, 2019 @01:02PM (#20919955)
I'm pretty sure there will be more than one commercial offer for Python2 support in the future.
Re:Sunsetting Python 2 by ueiuestu on Monday September 09, 2019 @09:26AM (#20917893)
This 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?

Re:Sunsetting Python 2 by ryl00 on Monday September 09, 2019 @09:50AM (#20918121)
I think there are plenty of programming languages (maybe even most of them?) which take backward compatibility as a very serious goal. Obviously there's a balance between "don't break user space!" and fixing major problems (e.g., C's gets()), and most of the major ones seem to lean toward the former.

At the company I work at, we've got a large amount of Fortran code from the '70s that works fine with the latest and greatest Fortran compilers (barring deprecation warnings which help guide refactoring efforts). Same with C/C++ from the '80s.

Re:Sunsetting Python 2 by pavelludiq on Monday September 09, 2019 @10:02AM (#20918225)
Common Lisp code tends to be very stable long term. Occasionally people dig out some old code from the 60s or from really old books and papers and it will just run on modern systems. Maybe with slight modifications since the standard was finalized in 1994 and there were some changes to the way scope works in common lisp compared to say the older mac lisp, but anything written since that is written in portable standard compliant common lisp is pretty much guaranteed to continue working while there are still people willing to maintain common lisp compilers for whatever hardware exists in the future. It's actually extremely comforting to be able to come back to a project after not touching it in a few years and have every test pass even if I upgraded all the dependencies(as long as I picked the right dependencies that is :), lispers tend to be pretty conservative about breaking changes in mature and popular libraries.
Re:Sunsetting Python 2 by toyg on Monday September 09, 2019 @09:44AM (#20918065)
"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.

Re:Sunsetting Python 2 by tannhaeuser on Monday September 09, 2019 @10:46AM (#20918666)
Anything based on real standards - C, POSIX/SUS shell, SQL, SGML, and others - is made without half-life and generational churn.
Re:Sunsetting Python 2 by oldmanhorton on Monday September 09, 2019 @11:09AM (#20918878)
Many compiled languages might have breaking changes at the language level but are still compatible at the dll/binary level. Java 1.0 and C# 1.0 code can still be compiled and run on modern JVMs and CLRs, and rust 2015 and 2018 work together as well.
Re:Sunsetting Python 2 by loeg on Tuesday September 10, 2019 @04:01AM (#20926022)
C18 is basically backwards compatible with C89. That's 30 years. The only function removed from stdlib is gets(), which was deprecated in C99.
Re:Sunsetting Python 2 by myself248 on Monday September 09, 2019 @10:48AM (#20918684)
Excel spreadsheets, which contain an astonishing amount of business logic, tend to be backwards-compatible far longer than the OSes that Excel itself runs on.

Food for thought, anyway.

Re:Sunsetting Python 2 by koreth1 on Monday September 09, 2019 @09:44AM (#20918063)
I would have said Java, but then they decided to shove modules down everyone's throat.
Re:Sunsetting Python 2 by Crinus on Monday September 09, 2019 @11:31AM (#20919078)
Wouldn'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.
Re:Sunsetting Python 2 by jerven on Tuesday September 10, 2019 @05:08AM (#20926347)
1.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.
Re:Sunsetting Python 2 by chrshawkes on Monday September 09, 2019 @11:48AM (#20919234)
I would say the Perl but then the Perl 6 fiasco made Python 3 look like a model citizen for upgrading code.
Re:Sunsetting Python 2 by mirchibajji on Monday September 09, 2019 @03:00PM (#20921180)
Perl5 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.
Re:Sunsetting Python 2 by johannes1234321 on Monday September 09, 2019 @07:04AM (#20917021)
> 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.

Re:Sunsetting Python 2 by bigiain on Monday September 09, 2019 @08:09AM (#20917369)
In 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?

Re:Sunsetting Python 2 by spurdoman77 on Monday September 09, 2019 @05:22AM (#20916508)
Personal 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.
Re:Sunsetting Python 2 by senko on Monday September 09, 2019 @06:00AM (#20916718)
There are companies offering extended support beyond EOL for version 2.
Re:Sunsetting Python 2 by jedberg on Monday September 09, 2019 @05:34AM (#20916593)
I meant my personal business use case.
[dead]
Re:Sunsetting Python 2 by gjm11 on Monday September 09, 2019 @10:12AM (#20918342)
To me, "for me" and "for my use case" mean subtly but genuinely different things.

"For me" highlights the fact that my preferences, character, skills, etc., are different from other people's. Something might work well for me but badly for someone else because I happen to be good at working around its quirks, or bad at noticing its faults, or just not interested in the things it doesn't do.

"For my use case" highlights the fact that the things I need to do are different from other people's. Something might be good for my use case but bad for others' because I don't need very high performance but they do, or because I need the gostak to be able to distim the doshes backwards but they don't.

If I move on to doing different work and someone else takes my place, I expect something that works well "for me" to continue being useful for me but not for them, and something that works well "for my use case" to be useful for them but not for me.

Re:Sunsetting Python 2 by normalhuman on Monday September 09, 2019 @11:04AM (#20918838)
Corparate-speak that makes its way into common language is frequently justified post-hoc by subtle differences in meaning like the ones you allude to. The problem is that these differences are personal and subjective. Ask someone else, they might have a different answer. I have had the same discussion multiple times over the equally meaningless and inelegant "going forward".

"Use case" comes from 90s software engineering: https://en.wikipedia.org/wiki/Use_case

Corporate-speak and cliché idioms makes one sound less clever, not more. It might temporarily signal belonging to some crowd (for example, the HN tech crowd), but in the long term it hampers one's ability to communicate in an effective and elegant way.

Re:Sunsetting Python 2 by meowface on Monday September 09, 2019 @11:21AM (#20918978)
This seems extremely pedantic. "Use case" as it's used today basically just means "case" or "situation" for a particular project or task or goal (edit: and for a particular individual/group/entity/organization). It's not business jargon or a buzzword term, even if perhaps it started off that way many decades ago.

I can think of countless annoying corporate buzzwords I see all the time on HN or at my job which are totally opaque and useless. "Use case" is two simple English words which anyone, including non-tech people, uses and clearly understands. This is not the hill to die on. I could link so many comments posted in the last week which are infinitely more buzzword-laden and irritating. If you really feel the dire necessity to chastise them, at least pick one of of those.

I do partly agree with you on "moving forward" or "going forward". I'm skeptical the situation was nearly as ambiguous as you suggest (it means "in the future", which is ambiguous, but it's no more ambiguous than saying "in the future", and anyone can easily request clarification if they hear "in the future"), but I had a few managers who said and wrote that like 30 times per day, and it does start to get on your nerves. Perhaps "use case" is similarly overused by some, but it also has a specific and clear meaning which would take longer to say/write than just using the term.

Re:Sunsetting Python 2 by logifail on Monday September 09, 2019 @01:16PM (#20920093)
> "Use case" is two simple English words which anyone, including non-tech people, uses and clearly understands

Source?

Where I am "use case" is definitely [still] tech jargon. I know very very few non-tech people who've ever heard it used, much less could give a definition for it.

Re:Sunsetting Python 2 by normalhuman on Monday September 09, 2019 @11:38AM (#20919142)
> This seems extremely pedantic. "Use case" as it's used today basically just means "case" or "situation" for a particular project or task or goal. It's not business jargon or a buzzword term, even if perhaps it started off that way many decades ago.

Notice that you are already in contradiction with the first criticism that I received in this thread, where a subtle difference in meaning was proposed.

> it means "in the future", which is ambiguous, but it's no more ambiguous than saying "in the future",

The main point is that it is totally unnecessary, we already have the future tense to talk about what will happen in the future.

The same applies here. Remove the phrase with "use case" and you get exactly the same meaning, with less words and less cringe.

Re:Sunsetting Python 2 by meowface on Monday September 09, 2019 @11:56AM (#20919319)
I see your point, but I think it's only redundant if the context of the use case(s) has already been established, in which case you can just refer to the thing itself (directly, or with demonstrative words). If anything, I think the much more redundant and cringey part is the "personal" in "my personal use case". "My use case" sounds fine to me.

"My use case" just generalizes "my {project, job, task, case}(s)". It's not ambiguous, because the intention is to be general. "For me" is a bit more general than that, though, and sometimes you want to be a little more specific.

The specificity hierarchy / subtle difference in meaning goes from "for me" (my attributes) -> "my use case" (my attributes + the case's attributes) -> "my [job/project/whatever]" -> "my [exact thing I'm specifically doing]". I think all can be valid, depending on the context. I maybe should've said "'case' or 'situation' for a particular project or task or goal done by a particular person (or group or organization)" instead (I was implying the latter part), but there's no contradiction here. By contrast, "moving forward" is typically implied and unnecessary no matter the context and can usually be cut as dead weight.

Re:Sunsetting Python 2 by gmfawcett on Monday September 09, 2019 @11:29AM (#20919055)
You're picking much too fine a nit here. The OP's use of "personal use case" is not a distracting example of corporate speak. I knew exactly what he meant when he wrote it, and his usage did help to clarify that he was basing his statements on his use of the technology, and not on his personal feelings about it.

But if if this is a hard-stop item for you at this juncture, then we should circle back... I'm sure we can align on this going forward. ;)

Re:Sunsetting Python 2 by normalhuman on Monday September 09, 2019 @11:34AM (#20919103)
> You're picking much too fine a nit here.

I think you feel that way because of the HN/tech echo chamber. Nobody says or feels the need to say "use case" outside of such circles.

> But if if this is a hard-stop item for you at this juncture, then we should circle back... I'm sure we can align on this going forward. ;)

Hehe ;)

Re:Sunsetting Python 2 by chipotle_coyote on Monday September 09, 2019 @01:59PM (#20920599)
I dunno -- if we're going to focus on the tics and quirks of the HN echo chamber, isn't this level of bikeshedding over the term "use case" kind of peak HN? :)
Re:Sunsetting Python 2 by gmfawcett on Monday September 09, 2019 @12:20PM (#20919541)
I don't know... I don't really consider myself part of the HN echo-chamber (who does, I guess?). I hear "use case" fairly regularly here at our university, among non-technical staff in our academic support units. Perhaps we've indoctrinated them over the years...

Regardless, I would argue that "use case" has a quite specific and useful meaning that goes beyond mere corp-speak. I wouldn't use in conversation at a neighbourhood barbecue, but in a technical context (like a discussion of Python) the usage seems perfectly fine.

Re:Sunsetting Python 2 by NoodleIncident on Monday September 09, 2019 @01:04PM (#20919965)
> Corparate-speak that makes its way into common language is frequently justified post-hoc by subtle differences in meaning like the ones you allude to.

You seem to have reversed cause and effect here. New words/phrases/jargon comes into common usage when it is useful for communicating something. The difference might be subtle, but people wouldn't use the word if they didn't think that it was an important distinction to make.

Re:Sunsetting Python 2 by sullyj3 on Monday September 09, 2019 @02:46PM (#20921032)
I really like the book "Death Sentence" by Don Watson, which eloquently skewers this kind of corporate jargon.
Re:Sunsetting Python 2 by bradenb on Monday September 09, 2019 @10:05AM (#20918263)
I don't necessarily think you're wrong, but HN has a history of comments like this that criticize other comments and add nothing to the discussion. Mine is another example, but since you got the ball rolling I figure I might as well chime in.

I think the grandparent's usage of "use case" was totally fine. It wasn't distracting and it didn't change my reading of that comment in any way, shape, or form.

Re:Sunsetting Python 2 by normalhuman on Monday September 09, 2019 @11:11AM (#20918899)
> HN has a history of comments like this that criticize other comments and add nothing to the discussion

I disagree. HN is a place that seems to pride itself on the quality of its discussions, and on a higher intellectual caliber when compared to other Internet discussion venues. Surely a good command of language is part of that?

Re:Sunsetting Python 2 by bradenb on Monday September 09, 2019 @12:43PM (#20919778)
Yes, it does pride itself on the quality of discussions. It also has done that just fine using the voting and flagging mechanisms. When I see comments criticizing others' comments I am always reminded of reddit. I think this is exactly what you're hoping to avoid when you come to HN.

Beyond that, who are we to judge what constitutes "good command of language?" Which language are we even talking about here? I don't think HN is going to become a better place by becoming more elitist.

Re:Sunsetting Python 2 by normalhuman on Monday September 09, 2019 @01:09PM (#20920016)
> When I see comments criticizing others' comments I am always reminded of reddit. I think this is exactly what you're hoping to avoid when you come to HN.

> I don't think HN is going to become a better place by becoming more elitist.

err...

Re:Sunsetting Python 2 by bradenb on Monday September 09, 2019 @02:22PM (#20920825)
What confuses you about what I said? “Not being reddit” and “not being elitist” are not mutually exclusive.

EDIT: I think it's clear nothing more needs to be said. Feel free to respond to this comment or not. I've said my piece.

Re:Sunsetting Python 2 by normalhuman on Monday September 09, 2019 @07:18PM (#20923575)
Come on now, don't be disingenuous. Of course they are mutually exclusive, because you mean "not being reddit" as in "we are better than reddit" -- an elitist stance.
Re:Sunsetting Python 2 by bradenb on Wednesday September 11, 2019 @12:52AM (#20936653)
I said I was done but I have to respond to this. Reddit prides itself on tangents and bickering and jokes. It’s great. I love Reddit. But I come to HN for focused technical discussion. I don’t believe one is inherently better than the other. Therefore, I believe it is not mutually exclusive.
Re:Sunsetting Python 2 by skywhopper on Monday September 09, 2019 @11:43AM (#20919197)
Hint for Hacker News commenters: 100% of the time, if your comment includes grammar or style advice, you can safely delete it and the discussion will lose no value. It's just a way to say "I'm smart" or "look at me" that sounds helpful but really isn't.

In this case, you could have said nothing.

Re:Sunsetting Python 2 by cheez on Monday September 09, 2019 @09:22AM (#20917848)
Are you sure you are indeed a normal human?
Re:Sunsetting Python 2 by jedberg on Monday September 09, 2019 @11:38AM (#20919140)
I used "use case" specifically because I was referring to business use cases.
Re:Sunsetting Python 2 by fortydegrees on Monday September 09, 2019 @10:05AM (#20918257)
Same with 'utilize' -> 'use'
Re:Sunsetting Python 2 by partialrecall on Monday September 09, 2019 @01:09PM (#20920008)
It's not restricted to tech. Cops do it too:

"This particular individual" -> "this person"

Re:Sunsetting Python 2 by ben509 on Monday September 09, 2019 @01:36PM (#20920333)
I've heard "orientate" for "orient" quite a few times, though maybe it was occidental.
Re:Sunsetting Python 2 by teekert on Monday September 09, 2019 @11:18AM (#20918954)
And 'A.I.' -> 'Algorithm'
Re:Sunsetting Python 2 by cheez on Monday September 09, 2019 @12:36PM (#20919710)
'A.I' -> 'Linear regression'

* ducks and runs

Re:Sunsetting Python 2 by decoyworker on Monday September 09, 2019 @08:30AM (#20917483)
>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?

Re:Sunsetting Python 2 by sidlls on Monday September 09, 2019 @08:35AM (#20917507)
Some people have full-time jobs and other obligations already that don't include time for this kind of effort.
Re:Sunsetting Python 2 by eropple on Monday September 09, 2019 @09:43AM (#20918047)
Your employer should be pitching in your effort. If they're not, and they're choosing to be a bad citizen, then on their own heads be it.