Re: lol
Compatibility modes are always the wrong thing. The compatibility break is to get rid of cruft and bad features, not add more.
Python 3 is basically where GvR said "ok, I made some mistakes designing things, but they're baked-in, so I can't change things without breaking compatibility" and eventually that was called Python 3.
It was originally "Python 2000" which shows how long it was under discussion.
I've done a ton of Python code, and it really isn't a big deal, and the changes are good ideas.
Go back to talking about something you might know something about.
Biting the hand that feeds IT
