A heads-up that Sunsetting of Python 2 is definitely(?) going to happen on Jan 1, 2020.
"That means that we will not improve it anymore after that day, even if someone finds a security problem in it. You should upgrade to Python 3 as soon as you can."
I *know* the Python community probably have to make this move. However, it won't be without problems. For example, in the past I have made use of Rawdog, which explicitly won't run on Python 3. There will be many packages like that.
Oh, BTW, "sunsetting" is horrible.
@sohkamyung IIRC there was some python library or sth whose dev was like "I'd rather maintain python2 myself than rewrite all my code in python3", right?
@Wolf480pl I'm afraid I have no knowledge of that, but it is possible.
However, in the long term, it's probably not a sustainable effort.
you only need bugfixes tho...
From my experience, if you are paid to develop $X which depends on $Y, and a bug in $Y makes it impossible for you to make progress with $X, you won't have a problem fixing that bug and submitting a patch. And if you're the only contributor, maintaining a fork should be easier than submittig patches, right?
@Wolf480pl Probably. Maybe we'll just have to see what happens by next year and whether developers step up to maintain Python 2.
@sohkamyung I remember being at Euro-Pycon 2007 and hearing Guido's talk about how we all needed to switch to Python 3.
Now, 12 years later, I'm finally doing it. 😳
At work we have a lot of Python 2 code that needs porting.
Luckily, there's the command-line tool '2to3' which analyzes your code for incompatibilities. It's been extremely helpful. And the bulk of what it finds can be solved with simple search-replaces, like print becoming print() or dict.keys() becoming list(dict.keys())