Python 2 to 3 was the last migration where the community actually had to suffer for it. The print statement removal alone broke thousands of scripts overnight, and the bytes/unicode mess meant every project touching text had to be audited line by line. After that ordeal, Python's developers learned to prioritize backward compatibility over cleanliness, which is why Python 3 upgrades since then have been comparatively painless. Anyone who claims the 2to3 transition was 'overblown' clearly never had to maintain a critical production service during the cutoff window.
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments