On 2009-01-30 11:40, Antoine Pitrou wrote: > Aahz <aahz <at> pythoncraft.com> writes: >> There's absolutely no reason not to have a 3.0.2 before 3.1 comes out. >> You're probably right that what Raymond wants to is best not done for >> 3.0.1 -- but once we've agreed in principle that 3.0.x isn't a true >> production release of Python for PEP6 purposes, we can do "release early, >> release often". > > It's a possibility. To be honest, I didn't envision us releasing a 3.0.2 > rather > than focusing on 3.1 (which, as others said, can be released in a few months > if > we keep the amount of changes under control). > > But then it's only a matter of naming. We can continue the 3.0.x series and > incorporate in them whatever was initially planned for 3.1 (including the > IO-in-C branch, the dbm.sqlite module, etc.), and release 3.1 only when the > whole thing is "good enough".
That would be my preference. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jan 30 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com