Greg Ewing wrote: > Paul Moore wrote: >> I'd rather argparse (or any library function) >> didn't call sys.exit on my behalf - it should raise an exception. > > Actually, sys.exit() *does* raise an exception (i.e. > SystemExit) that you can catch if you want. I was going to mention that. Between catching SystemExit, the '-i' switch to the interpeter and the PYTHONINSPECT environment variable, investigating applications that call sys.exit isn't *that* difficult. It's a far cry from the instant exits of a C level abort call. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia ---------------------------------------------------------------
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4