[Python-Dev] 2.7/3.2 release schedule

Raymond Hettinger python at rcn.com
Tue Nov 10 23:30:22 CET 2009

>> I personally think that decoupling the releases would be best, i.e.
>> not start thinking about 3.2 for another 6 months.

> The problem with that is that there is a period of time where 2.x has
> features which 3.x doesn't. My preference is to move back the whole
> schedule 6 months.

My preference is to decouple and let 2.7 go out 18 months after 2.6.
In general, 2.x users should not have to pay a price for whatever
we do with 3.x.


More information about the Python-Dev mailing list