Benjamin Peterson <benja...@python.org> writes: > I will leave a few initial comments.
Thank you. "Martin v. Löwis" <mar...@v.loewis.de> writes: > > In the case of <URL:http://bugs.python.org/issue1170> (“shlex have > > problems with parsing unicode”), the problem is apparently addressed > > by a patch, assigned to that issue since 2007-12-22. > > Apparently, or really? Did you review the patch? No. The bug report showed that others had already tried it and said it worked; and also, I don't consider myself qualified to review that particular patch. > > What is the procedure for finding out why an issue hasn't progressed? > > It's fairly simple: just read through the issue, and it should be > obvious. In the specific case, no committer has ever commented on the > issue, so chances are high that no committer has ever *seen* the > issue. Okay, so not obvious to someone (like me) who doesn't immediately know who is or is not a committer. Thanks for the clarification. > > I don't want to fill the bug database with such noise. > > And likely, posting to the issue won't be a way to find out, since no > committer would see your comment. I'll take that as confirmation that asking in this forum is the right procedure. -- \ “We spend the first twelve months of our children's lives | `\ teaching them to walk and talk and the next twelve years | _o__) telling them to sit down and shut up.” —Phyllis Diller | Ben Finney _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
