PEP0238 lament

[Edward C. Jones]

Guido van Rossum wrote:


> Thanks for the suggestion.  I think I'll do it this way: Python 3.x
> will be the first incompatible version, Python 2.x will require
> __future__ statements or other explicit ways to indicate that the
> programmer wants the new feature.
> 
> For less disturbing changes like nested scopes or generators (which
> would break only very small amounts of old code), we can introduce the
> new feature for real in the next release (e.g., nested scopes will be
> standard in 2.2, I expect generators will become standard in 2.3), but
> for devastatingly code-breaking changes like division, I'll wait until
> 3.0 before it becomes the law.


Good decision. The problem is solved as far as I am concerned.

<bad humor> 3.0 == 3000/100; 4.0 == 3000/10; 5.0 == 3000 </bad humor>

Ed Jones