Oh hey here’s a Python 2.7 end-of-life clock. I didn’t know they’d finally set the date for ending support. Is this for real?
If do, now I’m motivated to finally learn python and quit Matlab brandcuffs. I was put off by the schizophrenic state. pythonclock.org
Conversation
Replying to
Between the acting of a dreadful fork and the end-of-life, all the interim is like a phantasma, or a hideous dream. The BDFL and the mortal developers are then in council, and the state of Python, like to a little kingdom, suffers then the nature of an insurrection
4
Replying to
the 2.7-3.x superposition is one major reason why I stay away from Python
1
1
Show replies
Replying to
I’ve looked at it. Is it getting any significant degree of adoption?
1
1
Show replies
Replying to
Same, especially if 3+ fixes the whole conflicting layers of package management BS
Replying to
If you're just entering now, you're probably fine. Start on 3 and don't worry about it.
Moving an existing code base from 2->3 hurts, partially because you had to wait until all dependencies made the transition.





