X-Received: by 10.66.254.10 with SMTP id ae10mr4631748pad.32.1446697101599; Wed, 04 Nov 2015 20:18:21 -0800 (PST) X-Received: by 10.50.3.41 with SMTP id 9mr11771igz.7.1446697101526; Wed, 04 Nov 2015 20:18:21 -0800 (PST) Path: csiph.com!xmission!news.glorb.com!i2no3208467igv.0!news-out.google.com!fs1ni8575igb.0!nntp.google.com!i2no4468813igv.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.python Date: Wed, 4 Nov 2015 20:18:20 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=109.60.101.192; posting-account=19izYAoAAAA9JBIU5jzsuVhoPybSlW8- NNTP-Posting-Host: 109.60.101.192 References: <4b303213-62e2-42d4-b2f6-4fc1f6025944@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <4cb51da8-9331-4efe-87d3-dfe9c2ae0f8e@googlegroups.com> Subject: Re: How to handle exceptions properly in a pythonic way? From: zljubisic@gmail.com Injection-Date: Thu, 05 Nov 2015 04:18:21 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: csiph.com comp.lang.python:98274 > Which would you prefer? So if I am just checking for the ConnectionError in get_html and a new exception arises, I will have traceback to the get_html function showing that unhandled exception has happened. Now I have to put additional exception block for managing the new exception in the get_html function and I am covered. Is that what you wanted to say?