Really? Support for Python 2.7 was going to end in 2015, but they recently extended it to 2020.
What's the betting that in 2019 they won't extend it to 2025, followed shortly after by quietly dropping python 3 (or someone forking 2.7 to produce a compatible 2.8).
> Shouldn't new apps be written in 3 when possible?
There are no compelling reasons (for me at least) to change to what is in fact a different language which happens to use the same name.
When the Python 3 people eat their own dogfood by using a Python 3 toolchain, I might reconsider.
2014 + 5 years? Should your company fire you if you're wrong about an extension to 2025? You're going to cost them a lot of technical debt.
I always wondered how we got to the Y2K problem. That was a pretty hard deadline and people knew it was coming for years. How do people get away with creating problems like this?
Really? Support for Python 2.7 was going to end in 2015, but they recently extended it to 2020.
What's the betting that in 2019 they won't extend it to 2025, followed shortly after by quietly dropping python 3 (or someone forking 2.7 to produce a compatible 2.8).
> Shouldn't new apps be written in 3 when possible?
There are no compelling reasons (for me at least) to change to what is in fact a different language which happens to use the same name.
When the Python 3 people eat their own dogfood by using a Python 3 toolchain, I might reconsider.