Big problem: Confusing implementation with spec. One implementation should support BOTH
Posted Feb 10, 2011 2:46 UTC (Thu) by dwheeler
Parent article: Moving to Python 3
The real problem here is that the *spec* is being confused with its *implementation*. If there was a single implementation that accepted both Python2 and Python3, and let Python3 programs call Python2 programs, this would be a non-event. In fact, it'd be easy to do the transition, and we'd be mostly done.
Instead, there's one program that implements Python3, and a completely separate and incompatible engine that runs Python2.
Of course, this suggests a way out: Expand the Python2 system so it can run arbitrary Python3, and make it possible for Python3 programs to seamlessly call Python2. Then the problem would disappear.
to post comments)