[Patches] Patch to import.c

Jack Jansen jack@oratrix.nl
Sat, 03 Jun 2000 13:05:57 +0200


I'm a bit confused as to the current procedure for patches. It used to 
be that Guido said "yes" or "no", and that was it. Nowadays there seem 
to be very many people on the patches mailing list, and a patch gets a 
number of replies ranging from "don't do this" to "can't you do this
differently". I've tried to reply to all the issues, but I'm now completely
in the dark as to the status of my patches: I'm under the impression
that I've defended the case for my patches satisfactorily (hehe:-),
but people on the patch mailing list may think that I've some fixing
up to do.

As I didn't follow discussions on the new patch system: is there a
procedure and, if so, could it be documented on python.org/patches?
And if there isn't one: could one be designed and documented, please?

A time-limit on patch acceptance/rejection would also be nice, if
possible: I use the repository to sync my home machine and work
machine, which worked fine when Guido alone was responsible as he
worked what seems to be 19 hours per day, so patches usually ended up
in the repository before I had the chance to cycle from home to work
or vv., but with the new procedure it can apparently take a lot longer 
for patches to appear, so I may have to come up with another scheme to 
sync my multiple machines...
--
Jack Jansen             | ++++ stop the execution of Mumia Abu-Jamal ++++
Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++
www.oratrix.nl/~jack    | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm