[Python-Dev] another Python Bug Day?

Simon Cross hodgestar+pythondev at gmail.com
Wed Jan 7 00:18:46 CET 2009

On Tue, Jan 6, 2009 at 9:47 PM, Brett Cannon <brett at python.org> wrote:
> This is a years-old problem that is not going to be fixed overnight
> (unfortunately). But it is known and is being worked on (moving to a
> DVCS, writing up docs on the development process to cut down on bad
> patches, etc.).

It's encouraging to hear that it's been worked on. I assume the idea
is that eventually leiutenanents will maintain their own Python trees
in a similar way to what happens with the Linux kernel currently?

An interim solution that occurred to me is to give a few more people
enhanced access to the issue tracker and to create a
ready-for-committing keyword that these new issue wranglers could
apply to bugs that have patches and which they think are ready for
committing. Actual committers could then come along and search for the
given keyword to find things to examine for committing. This would
also act as testing ground for potential developers -- once committers
feel that the patches an issue wrangler approves really are
consistently good enough, they can consider promoting the issue
wrangler to a full developer.


More information about the Python-Dev mailing list