Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!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; 'interpreter': 0.05; 'received:verizon.net': 0.07; 'terry': 0.07; 'python': 0.08; 'exceptions': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:80.91.229.12': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'received:lo.gmane.org': 0.09; 'subclass': 0.09; 'am,': 0.12; 'exception': 0.12; 'why.': 0.15; 'this:': 0.15; 'except:': 0.16; 'frederic': 0.16; 'omitting': 0.16; 'reedy': 0.16; 'advance': 0.17; 'wrote:': 0.18; 'instance': 0.18; 'jan': 0.19; 'runs': 0.23; 'header:In-Reply-To:1': 0.23; 'code': 0.25; "i'm": 0.26; 'effect': 0.28; 'bare': 0.30; 'subject:?': 0.31; 'error': 0.31; 'to:addr:python-list': 0.32; 'instead': 0.33; 'header:User-Agent:1': 0.33; 'header:X-Complaints-To:1': 0.33; 'probably': 0.34; 'try:': 0.34; 'however,': 0.34; 'subject:How': 0.35; 'unless': 0.35; 'rather': 0.35; 'something': 0.36; 'doing': 0.37; 'but': 0.37; 'received:org': 0.37; 'could': 0.38; 'except': 0.39; "there's": 0.39; "it's": 0.39; 'subject:: ': 0.39; 'to:addr:python.org': 0.39; 'skip:_ 10': 0.40; 'really': 0.40; 'within': 0.60; 'your': 0.61; 'subject:. ': 0.65; 'contrary': 0.73; '11:57': 0.84; 'ridiculously': 0.84; 'subject:try': 0.84 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Terry Reedy Subject: Re: try - except. How to identify errors unknown in advance? Date: Wed, 16 Nov 2011 16:18:14 -0500 References: <1321462647.2315.31.camel@hatchbox-one> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: pool-74-109-121-73.phlapa.fios.verizon.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 In-Reply-To: <1321462647.2315.31.camel@hatchbox-one> X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 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: 26 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1321478316 news.xs4all.nl 6976 [2001:888:2000:d::a6]:38961 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:15791 On 11/16/2011 11:57 AM, Frederic Rentsch wrote: > If I don't know in advance which error to expect, but on the contrary > want to find out which error occurred, I can catch any error by omitting > the name: > > except: (handle) > > But now I don't have access to the error message 'e'. I'm sure there's a > way and it's probably ridiculously simple. Bare except is a holdover from when exceptions could be strings rather than an instance of a subclass of BaseException. A Python 3 interpreter in effect runs code within a try-except block something like this: try: except BaseException as __exception__: However, use Exception instead of BaseException in your code unless you REALLY know what you are doing and why. -- Terry Jan Reedy