Hi Python hackateers!
It looks like we finally have no more release blockers for 2.6.5rc2. I would like to tag the tree tonight for rc2 so that Martin can build the Windows installer for a release tomorrow. I am also moving the final release back to Friday March 19.
-Barry
On Tue, Mar 9, 2010 at 7:56 AM, Barry Warsaw barry@python.org wrote:
Hi Python hackateers!
It looks like we finally have no more release blockers for 2.6.5rc2. I would like to tag the tree tonight for rc2 so that Martin can build the Windows installer for a release tomorrow. I am also moving the final release back to Friday March 19.
Someone just commented on http://bugs.python.org/issue5228 (making functools.partial picklable to play nicer with the multiprocessing module)
I committed it a year ago to the trunk but didn't backport it to 26maint. Should I tell the guy that isn't the kind of thing we backport, that it is too late for a release candidate, or something else?
-Jack
Nevermind, I just read the full bug report and sure enough "Features such as this will not be backported to the 2.x branch" appears right there in the middle.
-Jack
On Tue, Mar 9, 2010 at 7:35 PM, Jack Diederich jackdied@gmail.com wrote:
On Tue, Mar 9, 2010 at 7:56 AM, Barry Warsaw barry@python.org wrote:
Hi Python hackateers!
It looks like we finally have no more release blockers for 2.6.5rc2. I would like to tag the tree tonight for rc2 so that Martin can build the Windows installer for a release tomorrow. I am also moving the final release back to Friday March 19.
Someone just commented on http://bugs.python.org/issue5228 (making functools.partial picklable to play nicer with the multiprocessing module)
I committed it a year ago to the trunk but didn't backport it to 26maint. Should I tell the guy that isn't the kind of thing we backport, that it is too late for a release candidate, or something else?
-Jack
participants (2)
-
Barry Warsaw
-
Jack Diederich