THE FORCED BACKWARD INCOMPATIBILITY

Do you see FIOC 3000 ever taking off as the de-facto FIOC standard, or we'll have around 2.x forever? I know that there's code that won't be updated, it's a shame having to maintain the older branch for ages to come. Shame on you, Guido.

It also worries me that not much stuff is getting updated at all, and even now stuff popping out right now is written for 2.x.

>>3
I always thought that Python's strength was its design, not its implementation. By that, you can conclude that Guido sucks at it all.

>>18
Buy why the fuck was it necessary to fork? It's going to be a maintenance nightmare. Was there any actual reason for it? The good way to do it is to have a single implementation, and pass a parameter to activate the new mode. Maybe have also a compile-time parameter to trim down the interpreter if you aren't going to use the legacy mode.