➜

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 rhettinger
Recipients rhettinger, yurzo
Date 2020-03-23.18:21:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584987716.51.0.391600348305.issue40033@roundup.psfhosted.org>
In-reply-to
Content 
> I assumed that Level1A should already be in scope while defining 
> the insides of Level1B. But it isn't.

That analysis is correct.  Class namespaces don't nest like functions do.  The "enclosing" namespace is globals, not the surrounding class.

This isn't a bug, but it is understandable why you might assume otherwise.
History
Date User Action Args
2020-03-23 18:21:56rhettingersetrecipients: + rhettinger, yurzo
2020-03-23 18:21:56rhettingersetmessageid: <1584987716.51.0.391600348305.issue40033@roundup.psfhosted.org>
2020-03-23 18:21:56rhettingerlinkissue40033 messages
2020-03-23 18:21:56rhettingercreate