[issue8841] getopt errors should be specialized

2015-04-09 Thread R. David Murray
R. David Murray added the comment: A python-ideas discussion was requested, but none has been linked to. So let's close this as uneeded. It can always be reopened if there is renewed interest. -- nosy: +r.david.murray resolution: -> rejected stage: needs patch -> resolved status: ope

[issue8841] getopt errors should be specialized

2014-02-03 Thread Mark Lawrence
Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue8841] getopt errors should be specialized

2013-05-12 Thread Mark Lawrence
Mark Lawrence added the comment: #11371 was closed on 2011-03-21 so what if anything needs doing here? -- nosy: +BreamoreBoy ___ Python tracker ___ ___

[issue8841] getopt errors should be specialized

2011-03-02 Thread Filip Gruszczyński
Filip Gruszczyński added the comment: Here it is: http://bugs.python.org/issue11371 -- ___ Python tracker ___ ___ Python-bugs-list mai

[issue8841] getopt errors should be specialized

2011-03-02 Thread Éric Araujo
Éric Araujo added the comment: > I suggested subclassing to solve the more general problem of the > caller being able to tell one getopt error from another, for which it > is a pretty common solution. Now I see what you meant and understand your request. optparse has five different error clas