BJörn Lindqvist wrote:
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
patche
Lee Harr wrote:
On 2005-02-03, BJörn Lindqvist <[EMAIL PROTECTED]> wrote:
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
On 2005-02-03, BJörn Lindqvist <[EMAIL PROTECTED]> wrote:
> 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
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
Frank Abel Cancio Bello wrote:
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 ac
Frank Abel Cancio Bello wrote:
> If I make some improvement to xmlrpclib module, where I should send this
> improvement to form part of next standard library release?
http://sourceforge.net/tracker/?group_id=5470&atid=305470
--
http://mail.python.org/mailman/listinfo/python-list
