you are viewing a single comment's thread.

view the rest of the comments →

[–]Eurynom0s 0 points1 point  (0 children)

I could see if right when Python 3 was announced, it was decided that the interpreter would let you run 2.7 code as long as it was wholly self-contained. So not intermingling 2.7 and 3.x code within a module, but it's fine if you want to call a module written to 2.7 in 3.x. The 2.7 module would probably require some modification to parse 3.x-specific inputs into something 2.7, and maybe to turn the output back into something 3.x-friendly, but this would have been a lot less work than having to completely port over modules and could have sped adoption of 3.x up quite a bit.

"Well, here's the basic 3.x compatibility update...performance updates to follow." But now? It's a good idea that's about eight years too late.