This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nelhage
Recipients andersk, bethard, eric.smith, nelhage, r.david.murray
Date 2010-07-22.23:40:25
SpamBayes Score 0.0008190852
Marked as misclassified No
Message-id <1279842032.0.0.281653044671.issue9334@psf.upfronthosting.co.za>
In-reply-to
Content
For what it's worth, I have trouble seeing this as anything but a bug. I understand the motivation of trying to catch user errors, but in doing so, you're breaking with the behavior of every other option parsing library that I'm aware of, in favor of an arbitrary heuristic that sometimes guesses wrong. That's not the kind of behavior I expect from my Python libraries; I want them to do what I ask them to, not try to guess what I probably meant.
History
Date User Action Args
2010-07-22 23:40:32nelhagesetrecipients: + nelhage, bethard, eric.smith, r.david.murray, andersk
2010-07-22 23:40:32nelhagesetmessageid: <1279842032.0.0.281653044671.issue9334@psf.upfronthosting.co.za>
2010-07-22 23:40:25nelhagelinkissue9334 messages
2010-07-22 23:40:25nelhagecreate