➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Alexander.Belopolsky
Recipients Alexander.Belopolsky, belopolsky, georg.brandl, lavajoe, r.david.murray
Date 2012-04-18.20:59:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <18AE1EFD-9081-416C-98EB-4C374CF041E2@gmail.com>
In-reply-to <1334782424.12.0.702649841399.issue10941@psf.upfronthosting.co.za>
Content 
I'll review your patch. 

On Apr 18, 2012, at 4:53 PM, Joe Peterson <report@bugs.python.org> wrote:

> 
> Joe Peterson <joe@skyrush.com> added the comment:
> 
> Ah.  I figured that one of the Python devs would be who would review it.  Is this the normal path for bugs?  Not to question the process, but I find it surprising, since I would think that it would cause a lot of bugs to stall out.  Also, I had no idea it was the submitter's responsibility to recruit reviewers.  And I am not quite sure how to go about this.  I do care about this bug (as it's pretty serious that it returns wrong results), so I am willing to do it.  Any wiki page or anything that describes the recruiting process or has more info?
> 
> ----------
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue10941>
> _______________________________________
History
Date User Action Args
2012-04-18 20:59:44Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, georg.brandl, belopolsky, r.david.murray, lavajoe
2012-04-18 20:59:43Alexander.Belopolskylinkissue10941 messages
2012-04-18 20:59:43Alexander.Belopolskycreate