About standard library improvement

[Frank Abel Cancio Bello]

Hi!
If I make some improvement to xmlrpclib module, where I should send this
improvement to form part of next standard library release?

Thank

 

[Steve Holden]

Hi!
If I make some improvement to xmlrpclib module, where I should send this
improvement to form part of next standard library release?

Thank

Well done! The standard place to lodge patches (whether for bug fixes
or improvements) is SourceForge. You'll need an account to submit
patches or bugs, IIRC. Once you've created your account, log in and go to

http://sourceforge.net/tracker/?group_id=5470&atid=305470

and click "Submit New".

regards
Steve

 

[=?ISO-8859-1?Q?BJ=F6rn_Lindqvist?=]

The process seem slow. I've submitted two patches and haven't gotten
any response so far, but it has only been three weeks. Other patches
seem to be idling for months. I'm not complaining, just want to know
why the process is so slow and what you can do when you submit
patches/bug reports to speed it up?

 

[Lee Harr]

The process seem slow. I've submitted two patches and haven't gotten
any response so far, but it has only been three weeks. Other patches
seem to be idling for months. I'm not complaining, just want to know
why the process is so slow and what you can do when you submit
patches/bug reports to speed it up?

I am certainly no expert, but I follow the lists. I recall
reading something recently that a lot of the logjam is the
need for people to look over other patches that have been
submitted. Something along the lines of ... if everyone
who submits a patch will just go through and check over
10 other patches we will have this backup sorted quickly.

So, if there are patches in the tracker that are in the
same general area as yours, or in another area about which
you have some knowledge, you chould check them out, and
comment on them and help out the process.

 

[Steven Bethard]

I am certainly no expert, but I follow the lists. I recall
reading something recently that a lot of the logjam is the
need for people to look over other patches that have been
submitted. Something along the lines of ... if everyone
who submits a patch will just go through and check over
10 other patches we will have this backup sorted quickly.

Yeah, a few of the python-devvers have agreed to this setup. And the
patch count has been lowered to 5. So if you really want to get your
patch reviewed, find 5 patches, look them over, test them out, and then
post your recommendations on how these patches should be handled to
python-dev. Then point them to the patch you'd like reviewed, and when
the generous python-devvers who have agreed to this setup get a chance,
they will review your patch.

STeVe

 

[Steve Holden]

The process seem slow. I've submitted two patches and haven't gotten
any response so far, but it has only been three weeks. Other patches
seem to be idling for months. I'm not complaining, just want to know
why the process is so slow and what you can do when you submit
patches/bug reports to speed it up?

BJörn:

I suspect you should join the python-dev list - you may well be able to
help much more effectively there.

regards
Steve

 

[Steve Holden]

The process seem slow. I've submitted two patches and haven't gotten
any response so far, but it has only been three weeks. Other patches
seem to be idling for months. I'm not complaining, just want to know
why the process is so slow and what you can do when you submit
patches/bug reports to speed it up?

BJörn:

I suspect you should join the python-dev list - you may well be able to
help much more effectively there.

regards
Steve