Alexander Belopolsky <alexander.belopol...@gmail.com> added the comment:
I'll review your patch. On Apr 18, 2012, at 4:53 PM, Joe Peterson <rep...@bugs.python.org> wrote: > > Joe Peterson <j...@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 <rep...@bugs.python.org> > <http://bugs.python.org/issue10941> > _______________________________________ ---------- nosy: +Alexander.Belopolsky _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10941> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
