3 ms·

There are still idiots on Github using Python 2 for new projects. These are usually academics who don't actually share any love for technology. Their code will

There are still idiots on Github using Python 2 for new projects. These are usually academics who don't actually share any love for technology. Their code will never be used by anyone.

upofadown 8y ago
There has been a pledge by the largest group of Python developers not to mess around with Python 2. So if you want your code to be able to just run forever without any concern for all the new and exciting language ideas being loaded into Python 3 then Python 2 is the logical choice.
- bakery2k 8y ago
  I've heard of this - people considering Python 2.7 as an "LTS" version of the language, receiving bug fixes but otherwise remaining unchanged for many years. I wonder, once 2.7 is EOL in a years time, whether the language developers will consider a "3.x LTS" release?
- pacifika 8y ago
  As long as you don’t need to connect to sites using https
Sir_Substance 8y ago
>Their code will never be used by anyone. Critical FORTRAN libraries are still the center of certain types of analysis, and they're often used by _everyone_ in the field. The reason for that stems from two issues: 1. Making accurate simulation libraries for things like weather formation, magnetic field formation or hydraulic fracturing requires crazy in depth knowledge of the systems you are modelling, and takes years of implementing and hypothesis testing to ensure they are accurate enough for academic use. 2. Academics are not software developers, they don't get paid for the software they write, they get paid for papers. They get no reward for rewriting those crazy indepth libraries every decade in the new language de-jour. This is a perfect example of why the python2 to python3 hard-cutoff transition was a terrible idea. "Just update your software" is something you can say to professional software developers with a straight face. You can't say it to academics, or mechatronics engineers, or real estate agents, or photographers, or _anyone else_ who has a job that benefits from a little bit of software but is mostly about delivering something other than software. Well, you can, but they're going to ignore you.

There are still idiots on Github using Python 2 for new projects. These are usually academics who don't actually share any love for technology. Their code will never be used by anyone.

upofadown 8y ago

There has been a pledge by the largest group of Python developers not to mess around with Python 2. So if you want your code to be able to just run forever without any concern for all the new and exciting language ideas being loaded into Python 3 then Python 2 is the logical choice.

bakery2k 8y ago
I've heard of this - people considering Python 2.7 as an "LTS" version of the language, receiving bug fixes but otherwise remaining unchanged for many years. I wonder, once 2.7 is EOL in a years time, whether the language developers will consider a "3.x LTS" release?
pacifika 8y ago
As long as you don’t need to connect to sites using https

Sir_Substance 8y ago

>Their code will never be used by anyone. Critical FORTRAN libraries are still the center of certain types of analysis, and they're often used by _everyone_ in the field. The reason for that stems from two issues: 1. Making accurate simulation libraries for things like weather formation, magnetic field formation or hydraulic fracturing requires crazy in depth knowledge of the systems you are modelling, and takes years of implementing and hypothesis testing to ensure they are accurate enough for academic use. 2. Academics are not software developers, they don't get paid for the software they write, they get paid for papers. They get no reward for rewriting those crazy indepth libraries every decade in the new language de-jour. This is a perfect example of why the python2 to python3 hard-cutoff transition was a terrible idea. "Just update your software" is something you can say to professional software developers with a straight face. You can't say it to academics, or mechatronics engineers, or real estate agents, or photographers, or _anyone else_ who has a job that benefits from a little bit of software but is mostly about delivering something other than software. Well, you can, but they're going to ignore you.