3 ms·
Bitterness isn't really a winning strategy. I thought the whole Python 3 thing was a huge problem. Lately I've been doing JS/Typescript dev and breaking change
by nl 4y ago
Bitterness isn't really a winning strategy.
I thought the whole Python 3 thing was a huge problem. Lately I've been doing JS/Typescript dev and breaking changes like this happen continually and no one blinks.
- anony23 4y agoWhat is the python3 thing?
- nl 4y agoPython 3 had incompatible changes with Python 2. You had to update your code, and for some years it meant lots of projects stayed on Python 2.
- TylerE 4y agoThe problem was never your code, really, it was the dependencies. Wasn't that hard for quite a while to find situations where dependency A was Py3 compatible and B was not (and the incompatibility went both ways, especially in early 3.x releases, you could NOT have one codebase that worked with both). Sometimes A dropped Py2 support before B gained Py3. Pain pain pain. Then add the increasing level of insanity as the answer to "python packaging sucks" was repeatedly to add yet another layer.