Python developers won’t let go of Python 2 (www.infoworld.com)

submitted 1 year ago by ruffsl@programming.dev to c/python@programming.dev

43 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] dingleberry@discuss.tchncs.de 12 points 1 year ago

Won't or can't?

[-] icedterminal@lemmy.world 9 points 1 year ago

Both. There are many breaking changes that can make your code completely incompatible. Some people won't bother to port their code. Others could be using an obscure or niche library that hasn't been updated for 3 and can't port their code.

[-] kogasa@programming.dev 4 points 1 year ago

Third category, software provided as part of an ancient service contract that nobody is allowed to touch, even though the service partner stopped offering support for this particular software years ago. Ask me how I know

[-] icedterminal@lemmy.world 2 points 1 year ago

Oof.

[-] dallen@programming.dev 1 points 1 year ago

At the old job I was using IronPython (2.7) to write Grasshopper plug-ins in the Rhino CAD software. Luckily, it was mostly responsible for kicking off Python3 and Go subprocesses.

Now, the worst I’m stuck with is 3.8 for one of our repos using PyTorch.