3 ms·
Because no one could ever be justified in moving to Python 3 for AsyncIO, f-strings, ordered dictionaries, assignment expressions, pathlib, new features in shut
by nuclear_eclipse 6y ago
Because no one could ever be justified in moving to Python 3 for AsyncIO, f-strings, ordered dictionaries, assignment expressions, pathlib, new features in shutil/tempfile/subprocess/etc, along with massive improvements to memory consumption, runtime performance, and overall stablility?
- ridiculous_fish 6y agoWas there something about the design of Python2 that would have prevented these features? Honest question.
- mixmastamyk 6y agoProbably not, but I’m still glad they did clean up. They could have done more.
- TylerE 6y agoUntil 3.8 py3 was slower than py2 in practically all benchmarks, and 3.8 is a marginal improvement at best. So I’m slapping a massive <citation needed> on your “massive” performance improvements
- nuclear_eclipse 6y agoWe switched a service from 2.7 to 3.5 and saw an immediate 45% reduction in memory usage and 20% reduction in runtime. That's massive IMO. We saw further (but smaller) performances benefits upgrading to 3.6, again when upgrading to 3.7, and expect to see even more with 3.8. https://youtu.be/0kXaLh8Fz3k?t=322 https://youtu.be/0kXaLh8Fz3k?t=322
- mark-r 6y agoPeople can and have been fine without those things for a long time. Many of them could have been added to Python2 without any trouble. And yet we still have a GIL.