> There's plenty of old code which people still depend on. System upgrades should not break your projects, or require you to go in and do surgery on scripts you

> There's plenty of old code which people still depend on. System upgrades should not break your projects, or require you to go in and do surgery on scripts you didn't write. On Linux land projects that depend on system libraries and `*-dev` packages break constantly across major versions. > That's a workaround. A solution would have allowed python 2 & 3 to coexist with no additional effort. You can do that if you make your python interpreter version explicit in your shebang. > I'm sorry, but all your arguments seem to boil down to the fact that there are ways to make python usable despite the extreme fragility of the toolset. A toolset that gave you a decade to upgrade with ample warnings is the opposite of fragile.