Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed1a.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <CALwzid=CdDj4m_bn0gPbS7eB_uD1VyKH-hoesqezS8re14idnQ@mail.gmail.com>
References: <0a89c96d-de62-42ad-be48-6107ce10d215@googlegroups.com> <roy-04A043.13393106062014@news.panix.com> <e2f76f44-8e3f-4ba0-9530-0d9d1b2bfdb4@googlegroups.com> <lmt0tc$4di$1@ger.gmane.org> <539396F3.5090508@stoneleaf.us> <mailman.10867.1402184850.18130.python-list@python.org> <roy-B72986.20120007062014@news.panix.com> <mailman.10871.1402189805.18130.python-list@python.org> <87lht73mdl.fsf@elektro.pacujo.net> <CAN1F8qWc6774ZpXdFPbKQOVw6T-0rkmZgPWEvUVqsdV+8QADUg@mail.gmail.com> <CALwzid=CdDj4m_bn0gPbS7eB_uD1VyKH-hoesqezS8re14idnQ@mail.gmail.com>
From: Ian Kelly <ian.g.kelly@gmail.com>
Date: Sun, 8 Jun 2014 12:07:34 -0600
Subject: Re: try/except/finally
To: Python <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.10894.1402250903.18130.python-list@python.org>
Lines: 44
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:72986

On Sun, Jun 8, 2014 at 12:02 PM, Ian Kelly <ian.g.kelly@gmail.com> wrote:
> On Sun, Jun 8, 2014 at 11:57 AM, Joshua Landau <joshua@landau.ws> wrote:
>> On 8 June 2014 08:12, Marko Rauhamaa <marko@pacujo.net> wrote:
>>>
>>> Does anyone have an example motivating a return from finally? It seems
>>> to me it would always be a bad idea as it silently clears all unexpected
>>> exceptions.
>>
>> In a general sense:
>>
>>     try:
>>         something_that_can_break()
>>         return foo() # before clean_up
>>     finally:
>>         clean_up()
>>         if default:
>>             return default() # after clean_up()
>>
>> What's the best replacement? Note: I've never done this.
>
> Why not just move the default out of the finally block?
>
>     try:
>         something_that_can_break()
>         return foo() # before clean_up
>     finally:
>         clean_up()
>     if default:
>         return default() # after clean_up()

Never mind, that doesn't work.  But you could do this:

    try:
        something_that_can_break()
        return foo() # before clean_up
    except ExpectedException:
        if default:
            return default() # after clean_up()
        else:
            raise
    finally:
        clean_up()

And then anything unexpected will be propagated instead of silenced.