PEP0238 lament

[David Boddie]

Guido van Rossum <guido at python.org> wrote in message news:<cp8zhd9gm9.fsf at cj20424-a.reston1.va.home.com>...
> "Bjorn Pettersen" <BPettersen at NAREX.com> writes:
> 
> > If there was to be a scheduled 3.0 release, any other source
> > incompatible changes that were seen as important would also have a
> > natural place to go.
> 
> 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.

To play devil's advocate, one might argue that by the time we get to
Python 3.0 (four years?) anyone wanting the new form of the / operator
will be used to explicitly asking for it.

So, if you're already resigned to that then just changing __future__
to something else like

from __behaviour__ import float_division

would be just as easy, and wouldn't break existing code. <wink>

just-lie-down-in-front-of-the-bulldozer-while-we-go-for-a-drink-ly
y'rs - David