On Tue, Jan 27, 2009 at 11:29, Barry Warsaw <ba...@python.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Jan 27, 2009, at 2:05 PM, Guido van Rossum wrote: > >> On Tue, Jan 27, 2009 at 11:00 AM, Raymond Hettinger <pyt...@rcn.com> >> wrote: >>> >>> With the extensive changes in the works, Python 3.0.1 is shaping-up to be >>> a >>> complete rerelease of 3.0 with API changes and major usability fixes. It >>> will fully supplant the original 3.0 release which was hobbled by poor IO >>> performance. >>> >>> I propose to make the new release more attractive by backporting several >>> module improvements already in 3.1, including two new itertools and one >>> collections class. These are already fully documented, tested, and >>> checked-in to 3.1 and it would be ashamed to let them sit idle for a year >>> or >>> so, when the module updates are already ready-to-ship. >> >> In that case, I recommend just releasing it as 3.1. I had always >> anticipated a 3.1 release much sooner than the typical release >> schedule. >
A quick 3.1 release also shows how committed we are to 3.x and that we realize that 3.0 had some initial growing pains that needed to be worked out. > I was going to object on principle to Raymond's suggestion to rip out the > operator module functions in Python 3.0.1. I thought it was for 3.1? > I have no objection to ripping > them out for 3.1. > > If you really think we need a Python 3.1 soon, then I won't worry about > trying to get a 3.0.1 out soon. 3.1 is Benjamin's baby :). > Depending on what Benjamin wants to do we could try for something like a release by PyCon or at PyCon during the sprints. Actually the sprint one is a rather nice idea if Benjamin is willing to spend sprint time on it (and he is sticking around for the sprints) as I assume you, Barry, will be there to be able to help in person and we can squash last minute issues really quickly. > If OTOH we do intend to get a 3.0.1 out, say by the end of February, then > please be careful to adhere to our guidelines for which version various > changes can go in. For example, the operator methods needs to be restored > to the 3.0 maintenance branch, and any other API changes added to 3.0 need > to be backed out and applied only to the python3 trunk. If you have the time for it, Barry, I am +1 on an end of February 3.0.1 with a March/April 3.1 if that works for Benjamin. -Brett _______________________________________________ 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
