Overarch3784 ( @Overarch3784@kbin.social ) 17•9 months agoI think the biggest problem would be libraries which are not available in 3.x. I just rewrote a python script some time ago and the syntax changes were pretty easy to change with search and replace.
Dr Cog ( @Dr_Cog@mander.xyz ) 4•9 months agoI don’t see a problem. For one, it’s been 15 years: the vast majority of libraries have been ported by now. And like you said, you can fix the syntax with basically a find/replace script, so any stragglers can be modified easily.
There really isn’t any excuse to still be using Python 2 anymore
Gamma ( @GammaGames@beehaw.org ) English10•9 months agoI had no idea, never having to deal with library updates must be nice 😆
- dingleberry ( @dingleberry@discuss.tchncs.de ) 6•9 months ago
Won’t or can’t?
dallen ( @dallen@programming.dev ) English1•9 months agoAt 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.