[issue3079] sys.exit() called from optparse - bad, bad, bad

Phillip M. Feldman report at bugs.python.org
Fri Oct 16 02:03:47 CEST 2009


Phillip M. Feldman <pfeldman at verizon.net> added the comment:

The current behavior of optparse is contrary to how most of Python
works. optparse should throw a named exception that can be trapped and
identified by the calling program.  Doing a SystemExit is unacceptable.
 I can't believe that this is such a hard thing to fix.

----------
nosy: +pfeldman at verizon.net

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3079>
_______________________________________


More information about the Python-bugs-list mailing list