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 Phillip.M.Feldman@gmail.com
Recipients Phillip.M.Feldman@gmail.com, georg.brandl, ggenellina, pitrou, skip.montanaro
Date 2009-10-16.00:03:45
SpamBayes Score 1.37538e-06
Marked as misclassified No
Message-id <1255651427.38.0.0608580673501.issue3079@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2009-10-16 00:03:48Phillip.M.Feldman@gmail.comsetrecipients: + Phillip.M.Feldman@gmail.com, skip.montanaro, georg.brandl, ggenellina, pitrou
2009-10-16 00:03:47Phillip.M.Feldman@gmail.comsetmessageid: <1255651427.38.0.0608580673501.issue3079@psf.upfronthosting.co.za>
2009-10-16 00:03:46Phillip.M.Feldman@gmail.comlinkissue3079 messages
2009-10-16 00:03:46Phillip.M.Feldman@gmail.comcreate