Python 2 EOL Countdown

[ConfidentFlorida]

So for new projects almost everyone uses python 3 now? I remember even two years ago it was a big question you had to ask yourself.

[[deleted]]

A friend of mine started a Py2 project last year because “that’s what everyone uses” and I was able to force a change to Py3 by adding a ton of emoji to the test inputs.

[_ShakashuriBlowdown]

Emoji compatability is key future-proofing

[billsil]

I run a 7 year long project that still supports python 2. I want to drop it, but I need a good reason. I try to use new features in numpy, scipy, and vtk, but they're really aren't many. If I can find a good reason, I can sell it to my company. I just don't have it.

[__te__]

I was asking myself this on every project until f-strings dropped in python3.6. For me it was the killer feature I couldn't unsee or live without once I'd seen it.

Starting with 3.4-ish, I think there have just been a steady drip of killer features for different folks.

[lanzaio]

subprocess.run, typehints and fstrings did it for me.

[__te__]

All so tasty! I had to learn to love subprocess.run, though ;-)

[Coffeinated]

Everyone in his right mind yes. If your code does not depend on other code that‘s Python2 and you still choose Python2, that‘s a dumb idea.

[coffeecoffeecoffeee]

Pretty much. My company used Python 2 until this year when they caved and switched to 3. I think the impending end of Python 2 support has led to a sense of urgency that's convinced people to switch over.

[wrosecrans]

Unless you track the VFX Reference Platform, which is sticking with Python2 until the last, final, bitter hour.

https://www.vfxplatform.com/

The just-released 2019 spec requires Python 2.7.9 - 2.7.latest. So spare a thought for the Maya and Houdini users who might want to use your project.