report at bugs
Apr 18, 2012, 1:59 PM
Post #4 of 17
Alexander Belopolsky <alexander.belopolsky [at] gmail> added the comment:
[issue10941] imaplib: Internaldate2tuple produces wrong result if date is near a DST change
[In reply to]
I'll review your patch.
On Apr 18, 2012, at 4:53 PM, Joe Peterson <report [at] bugs> wrote:
> Joe Peterson <joe [at] skyrush> 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 [at] bugs>
Python tracker <report [at] bugs>
Python-bugs-list mailing list