submitting patches against 1.6a2

[Paul Schreiber]

Thomas Wouters wrote:

>> I patched a number of bugs in urllib.py way back when -- in June, I 
>> think. That was before the BeOpen announcement.
>
>> I emailed the patch to patches at python.org. I included the disclaimer. I 
>> made the patch into a context diff.
>
>> I didn't hear back from anyone.
>
>It's possible, but not certain, that your patch ended up in the SF patch
>manager -- the patches list was 'moved' there to improve patch-handling, but
>your patch might have been missed in the move. If it was moved, it's pretty
>likely it was accepted as-is or used as the basis of another patch. You can
>try browsing through the entire list of patches, but that's a pretty big
>list. You can also download the CVS tree and see if it includes your patch,
>or at least adresses the same issues as your patch did (you can 'view' the
>CVS tree without downloading it at sourceforge:
>
>http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi?cvsroot=python

Nope. I've been checking the tree rather impatiently, and it hasn't 
appeared, although other changes have been made to urllib.py.

>You can find the rest of the information here:
>
>http://sourceforge.net/projects/python

Yeah, I have a sourceforge account.

>> Should I resubmit? Where should I send the patch to?
>
>Depending on when your patch was accepted (before or after the move to
>BeOpen) it might or might not be included in the 1.6b1 release which is
>expected sometime today. (again :)

Okay, so should I resubmit? I emailed Andrew (who appears to own the 
module) 2-3 weeks ago, but didn't hear from him.


Paul