➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author oleksandr.suvorov
Recipients Mark.Shannon, oleksandr.suvorov, pablogsal
Date 2020-05-22.11:10:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CACYZ_wLEL9o2FBCjmJELZCK6XLRjOHcE2HX+P8n2R4ecCwkdJw@mail.gmail.com>
In-reply-to <1590145715.14.0.407414166001.issue40728@roundup.psfhosted.org>
Content 
But then why I still can access this variable? Shouldn't it then be
resulting in NameError as it's undefined variable at this point of time?
I think UnboundError creates more confusing here, as it's either the
variable should exist and have a value or it should be unknown and result
in NameError at this point.

On Fri, May 22, 2020 at 1:08 PM Pablo Galindo Salgado <
report@bugs.python.org> wrote:

>
> Change by Pablo Galindo Salgado <pablogsal@gmail.com>:
>
>
> ----------
> nosy: +Mark.Shannon
> resolution:  -> not a bug
> stage:  -> resolved
> status: open -> closed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue40728>
> _______________________________________
>
History
Date User Action Args
2020-05-22 11:10:40oleksandr.suvorovsetrecipients: + oleksandr.suvorov, Mark.Shannon, pablogsal
2020-05-22 11:10:40oleksandr.suvorovlinkissue40728 messages
2020-05-22 11:10:40oleksandr.suvorovcreate