[issue40728] UnboundLocalError as a result of except statement variable re-assignment

[Oleksandr Suvorov]

Oleksandr Suvorov <susliko at gmail.com> added the comment:

What I mean is why would it need to shadow function variable name if after
except block it's always unbound, what is the reason and why this is
expected?

On Fri, May 22, 2020 at 1:19 PM Oleksandr Suvorov <report at bugs.python.org>
wrote:

>
> Oleksandr Suvorov <susliko at gmail.com> added the comment:
>
> but if exc variable is only available in except block why then it shadows
> the function variable name?
>
> On Fri, May 22, 2020 at 1:15 PM Christian Heimes <report at bugs.python.org>
> wrote:
>
> >
> > Christian Heimes <lists at cheimes.de> added the comment:
> >
> > UnboundLocalError is a subclass of NameError. You are getting a more
> > specific error here.
> >
> > >>> UnboundLocalError.__mro__
> > (<class 'UnboundLocalError'>, <class 'NameError'>, <class 'Exception'>,
> > <class 'BaseException'>, <class 'object'>)
> >
> > ----------
> > nosy: +christian.heimes
> >
> > _______________________________________
> > Python tracker <report at bugs.python.org>
> > <https://bugs.python.org/issue40728>
> > _______________________________________
> >
>
> ----------
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue40728>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue40728>
_______________________________________