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 lavajoe
Recipients belopolsky, georg.brandl, lavajoe, r.david.murray
Date 2012-04-18.20:53:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334782424.12.0.702649841399.issue10941@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2012-04-18 20:53:44lavajoesetrecipients: + lavajoe, georg.brandl, belopolsky, r.david.murray
2012-04-18 20:53:44lavajoesetmessageid: <1334782424.12.0.702649841399.issue10941@psf.upfronthosting.co.za>
2012-04-18 20:53:43lavajoelinkissue10941 messages
2012-04-18 20:53:43lavajoecreate