Issue 1170: Unicode for ‘shlex’
Howdy all, What is the procedure for finding out why an issue hasn't progressed? I don't want to fill the bug database with such noise. 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. There is no indication in the report why it's not yet applied. I'd really like this fixed in the 2.x series if possible. -- \ “… whoever claims any right that he is unwilling to accord to | `\ his fellow-men is dishonest and infamous.” —Robert G. | _o__) Ingersoll, _The Liberty of Man, Woman and Child_, 1877 | Ben Finney
2009/8/21 Ben Finney <ben+python@benfinney.id.au>:
In this case, it's probably because no one officially maintains the shlex module at the moment.
I will leave a few initial comments.
I'd really like this fixed in the 2.x series if possible.
-- Regards, Benjamin
Benjamin Peterson <benjamin@python.org> writes:
I will leave a few initial comments.
Thank you. "Martin v. Löwis" <martin@v.loewis.de> writes:
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.
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'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
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.
Apparently, or really? Did you review the patch? Regards, Martin
2009/8/21 Ben Finney <ben+python@benfinney.id.au>:
In this case, it's probably because no one officially maintains the shlex module at the moment.
I will leave a few initial comments.
I'd really like this fixed in the 2.x series if possible.
-- Regards, Benjamin
Benjamin Peterson <benjamin@python.org> writes:
I will leave a few initial comments.
Thank you. "Martin v. Löwis" <martin@v.loewis.de> writes:
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.
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'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
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.
Apparently, or really? Did you review the patch? Regards, Martin
participants (3)
-
"Martin v. Löwis" -
Ben Finney -
Benjamin Peterson