[Python-3000] After 2.6 should be 3.0

[Guido van Rossum]

On 4/19/06, Josiah Carlson <jcarlson at uci.edu> wrote:
> Again, in my opinion, features should necessitate the Python 3.x release.
> Is the integer division change sufficient to necessitate 3.0 after 2.6?
> Goodness, I hope not.

It's the other way around. int/int alone isn't enough to trigger 3.0;
but only 3.0 can change the semantics of int/int. (This has been
promised quite a long time ago and I don't think it ought to be
revised.)

> I understand the dislike of repeated __future__ imports (I was using
> 'from __future__ import generators' for longer than I would have liked
> to), but this particular feature doesn't seem to imply to me that 3.0
> should come out sooner, rather it says that people should be made aware
> of the integer division operation change, and it should make it into the
> 2.x series (how long have we been talking about integer division changes?)

No. The timeline was fixed in the PEP. We can't change this without
seriously affecting Python's image to those users who care about
backwards compatibility.

--
--Guido van Rossum (home page: http://www.python.org/~guido/)