[Python-Dev] Python-3000 upgrade path

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Feb 25, 2007, at 3:49 PM, Neal Norwitz wrote:

> The time schedules in PEP 361 (2.6 release schedule) and what Guido
> has said for 3k (from what I remember) are roughly:
>
>   April 2007 - 3.0 PEPs and features accepted/decided
>  June 2007 - 3.0a1 - basic (most) features implemented
>  Dec 2007 - 2.6a1
>  Apr 2008 - 2.6 final
>  July 2008 - 3.0 final
>
> Even if we slip these schedules, as long as we keep them in relative
> order, we can keep 2.6 robust, while also offering many of the 3k
> features.

I said semi-jokingly that the first release of Py3k should be / 
literally/ called Python 3000.  Then each successive stabilizing  
release should drop a zero -- e.g. Python 3000, then Python 300, then  
Python 30.  By the time we get to Python 3 all we should basically  
have to do is change the defaults of whatever Python 2.x version is  
out to complete the transition.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iQCVAwUBReJgp3EjvBPtnXfVAQIZQgP+K5iWRTYHYvqb3cAUFJw/yDDiz5JPG94x
XdMEnCUXwJVyU30q3FGSNeaz3hwQq7xgJuH5DBRHnGkxp7H/K42ft/KXnJVGnkt4
Kai8e26+zBXmCSCTVdJyKhpAiiFAqKTw26+L+a1jyJdSbUnly3coBAvRaOS9oQn6
QcVfx5vCOsM=
=o7Ux
-----END PGP SIGNATURE-----