RetroSearch Browse

Sat Aug 22 11:16:47 CEST 2009 · http://mail.python.org/pipermail/python-dev/2009-August/091309.html

> 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.

> 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.

> 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?

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2009-August/091309.html below:

[Python-Dev] Issue 1170: Unicode for ‘shlex’