3 ms·

I mean python is basically the prime example of how to poorly manage version upgrades with their failure of 2 => 3.

• bigiain 6y ago
  They were just desperate to do a better job of screwing up than Perl with it's 5 => 6 updates... <grin>
  • masklinn 6y ago
    As we can see from the Perl ecosystem having completely moved over to the extent that Perl 5 is now out of support while Python is still mired in the update.
    • takeda 6y ago
      That's funny, because I see the opposite. Perl 6 was a failure that had to be spun into a separate language and people stayed with perl 5, recently work on perl 7 started, but as far as I know perl 5 is still the version in use, recently FreeBSD forced me to update perl to version 5.32. Regarding Python, I no longer see 2.7 in the wild (I have no doubt it is still in some places) all projects I'm working on are in Python 3. AWS Lambda supports 3.8 (which is the latest stable version), Ubuntu comes with 3 installed by default. FreeBSD set 3.7 as default, depreciated and will remove 2.7 completely by the end of this year. Many Python 3 packages were released as python 3 only, the packages that that previously supported 2 dropped their support. Currently running 2.7 is a liability. Not as much that it is EOL and there are no security fixes anymore, but also packages dropping support (which is IMO a bigger deal).
      • masklinn 6y ago
        Yes my comment was ironic.
        • takeda 6y ago
          ah, feeling dumb now :)
• barumi 6y ago
  Can you provide a single example that supports your thesis that migration from Python 2 to 3 was poorly managed semver-wise? If anything, Python is chastised for having maintained two major versions in parallel without giving any compelling reason to force major rewrites on the while ecosystem.