Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.001 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'default.': 0.09; 'option,': 0.09; 'subject:Why': 0.09; 'subject:module': 0.09; 'cc:addr:python-list': 0.11; 'belongs': 0.16; 'from:addr:cs': 0.16; 'from:addr:zip.com.au': 0.16; 'from:name:cameron simpson': 0.16; 'make,': 0.16; 'message-id:@cskk.homeip.net': 0.16; 'ought': 0.16; 'received:211.29': 0.16; 'received:211.29.132': 0.16; 'received:optusnet.com.au': 0.16; 'received:syd.optusnet.com.au': 0.16; 'simpson': 0.16; 'stupidity': 0.16; 'subject:argparse': 0.16; 'to:addr:pearwood.info': 0.16; 'to:addr:steve+comp.lang.python': 0.16; "to:name:steven d'aprano": 0.16; 'wrote:': 0.18; 'code,': 0.22; 'cc:addr:python.org': 0.22; 'header:User-Agent:1': 0.23; 'config': 0.24; "shouldn't": 0.24; 'cc:2**0': 0.24; 'cc:no real name:2**0': 0.24; 'header:In-Reply- To:1': 0.27; 'raise': 0.29; "d'aprano": 0.31; 'libraries': 0.31; 'shelf': 0.31; 'steven': 0.31; 'framework': 0.33; 'subject:the': 0.34; 'could': 0.34; 'but': 0.35; 'there': 0.35; 'received:com.au': 0.36; 'charset:us-ascii': 0.36; 'subject:?': 0.36; 'should': 0.36; 'application': 0.37; 'received:211': 0.38; 'catch': 0.60; 'content-disposition:inline': 0.62; 'more': 0.64; 'frank': 0.68; 'life.': 0.83; 'hydrogen': 0.84 Date: Fri, 28 Jun 2013 09:34:48 +1000 From: Cameron Simpson To: Steven D'Aprano Subject: Re: Why is the argparse module so inflexible? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51ccc190$0$29999$c3e8da3$5496439d@news.astraweb.com> User-Agent: Mutt/1.5.21 (2010-09-15) References: <51ccc190$0$29999$c3e8da3$5496439d@news.astraweb.com> X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.0 cv=Q6eKePKa c=1 sm=1 a=wom5GMh1gUkA:10 a=I0cP0X-GMOAA:10 a=kj9zAlcOel0A:10 a=vrnE16BAAAAA:8 a=ZtCCktOnAAAA:8 a=_UKPi1JAgJMA:10 a=kZ7UWmmPAAAA:8 a=K4pBxFx3xxF1dgNFo3MA:9 a=CjuIK1q_8ugA:10 a=pyH5b1fOeEsA:10 a=ChdAjXE5lkUvdteQbhpnkQ==:117 Cc: python-list@python.org X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 18 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1372376101 news.xs4all.nl 15979 [2001:888:2000:d::a6]:58156 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:49352 On 27Jun2013 22:49, Steven D'Aprano wrote: | [rant] | I think it is lousy design for a framework like argparse to raise a | custom ArgumentError in one part of the code, only to catch it elsewhere | and call sys.exit. At the very least, that ought to be a config option, | and off by default. | | Libraries should not call sys.exit, or raise SystemExit. Whether to quit | or not is not the library's decision to make, that decision belongs to | the application layer. Yes, the application could always catch | SystemExit, but it shouldn't have to. +1 -- Cameron Simpson There is more stupidity than hydrogen in the universe, and it has a longer shelf life. - Frank Zappa