Re: [Python-Dev] Re: httplib.py vs 222
Jeremy Hylton jeremy@alum.mit.edu writes:
"MH" == Michael Hudson mwh@python.net writes:
MH> I'm tempted to just dump the trunk's version of httplib.py onto MH> the release branch. Poring over logs reveals that nearly every MH> checkin is marked as a bugfix candidate (occasionally with a MH> question mark).
MH> Certainly it seems ot would be easier to work the checkins that MH> aren't bugfixes out of the trunk than work those that are into MH> the branch, if you see what I mean.
MH> But I've never used httplib, so I thought I should ask here MH> first (and Cc: the people responsible for most of the changes).
MH> Comments?
I think it makes sense to make httplib identical. The changes to httplib have all been intended to make it more robust.
My one worry is that a set of changes I made may have broken pipelined https requests in order to fix a different set of bugs. I had intended to check whether pipelined https requests actually worked in 2.2.1.
Ooh! Delagation! This is now your problem :)
If you (or someone else) don't get to it before 2.2.2's release date, I'll just dump the trunk's version into the branch.
Cheers, M.
If you (or someone else) don't get to it before 2.2.2's release date, I'll just dump the trunk's version into the branch.
Why don't you do that now, so we don't forget that part.
--Guido van Rossum (home page: http://www.python.org/~guido/)
Guido van Rossum guido@python.org writes:
If you (or someone else) don't get to it before 2.2.2's release date, I'll just dump the trunk's version into the branch.
Why don't you do that now, so we don't forget that part.
Sure. It seems Jeremy had already backported quite a pile of these fixes back in July.
Cheers, M.
participants (2)
-
Guido van Rossum -
Michael Hudson