RetroSearch Browse

Tue Sep 29 22:38:23 CEST 2009 · https://mail.python.org/pipermail/python-dev/2009-September/092310.html

On Tue, Sep 29, 2009 at 2:31 PM, Paul Moore <p.f.moore at gmail.com> wrote:
> 2009/9/28 Yuvgoog Greenle <ubershmekel at gmail.com>:
>> 1. There is no chance of the script killing itself. In argparse and optparse
>> exit() is called on every parsing error (btw because of this it sucks to
>> debug parse_args in an interpreter).
>
> That one does worry me. I'd rather argparse (or any library function)
> didn't call sys.exit on my behalf - it should raise an exception. Is
> it actually true that argparse exits? (I can imagine that it might if
> --help was specified, for example. An exception may not be right here,
> but I still don't like the idea of a straight exit - I've used too
> many C libraries that think they know when I want to exit).
>

+1

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2009-September/092310.html below:

[Python-Dev] PEP 389: argparse - new command line parsing module