[issue8841] getopt errors should be specialized

[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: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8841] getopt errors should be specialized

[Mark Lawrence]

Changes by Mark Lawrence :


--
nosy:  -BreamoreBoy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8841] getopt errors should be specialized

[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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8841] getopt errors should be specialized

[Filip Gruszczyński]

Filip Gruszczyński  added the comment:

Here it is: http://bugs.python.org/issue11371

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8841] getopt errors should be specialized

[É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 classes and argparse has two, but they don’t bubble up to the 
caller, they’re caught and turned into error messages.  getopt is different, 
since it require its users to do the gruntwork, so having different exceptions 
for different user errors would be helpful.  Compatibility would not be an 
issue, we’d just make all classes inherit from GetoptError so that except 
clauses would still work.  I think you should take this to the python-ideas 
mailing list: Do other getopt users need this functionality?  What subclasses 
should there be?

Filip: Localization of error messages in getopt is another enhancement.  Would 
you mind opening another report and moving your patch there?  Thanks.

--
title: GetoptError strings should be localized -> getopt errors should be 
specialized

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com