The finally clause is not executed when an exception occurs and 'raise' keyword is used in except clause.

The 'finally' clause is not executed when an exception occurs and 'raise' keyword is used in except clause.

I cannot reproduce.

>>> try:
...     1/0
... except:
...     print('except')
...     raise
... finally:
...     print('finally')
... 
except
finally
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
ZeroDivisionError: division by zero

Could you please provide an example code?

I have attached a file as an example. The finally clause is not getting executed if we make use of raise keyword in except clause. It should have been executed in this case case, right?

It works as expected (the print statement in the "finally" clause is executed) for me.

Really? Why is it not working for me then? I am using the latest version of
VS code application. I have attached a screenshot,have a look at this.

On Tue, Jul 27, 2021 at 6:22 PM Paul Moore <report@bugs.python.org> wrote:

>
> Paul Moore <p.f.moore@gmail.com> added the comment:
>
> It works as expected (the print statement in the "finally" clause is
> executed) for me.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue44746>
> _______________________________________
>

The output from the print statement in the finally block is before the traceback, you need to scroll back in the output buffer in VS Code.

Confirmed that it is working in Linux. I assume Paul has tested it under Windows, and it sounds like Ronald has tested it in VS Code as well.

I'm closing this as Not A Bug.

Priyanshu, if you disagree and can replicate the error, this time checking the output buffer, please reply with a new example.

Ok, I'll check it out.
Thank you for the response.

On Tue, 27 Jul, 2021, 20:36 Steven D'Aprano, <report@bugs.python.org> wrote:

>
> Steven D'Aprano <steve+python@pearwood.info> added the comment:
>
> Confirmed that it is working in Linux. I assume Paul has tested it under
> Windows, and it sounds like Ronald has tested it in VS Code as well.
>
> I'm closing this as Not A Bug.
>
> Priyanshu, if you disagree and can replicate the error, this time checking
> the output buffer, please reply with a new example.
>
> ----------
> resolution:  -> not a bug
> stage:  -> resolved
> status: open -> closed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue44746>
> _______________________________________
>