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 terry.reedy
Recipients Hibou57, Mariatta, Roscoe R. Higgins, brett.cannon, cheryl.sabella, docs@python, ezio.melotti, miss-islington, nanjekyejoannah, terry.reedy, veky
Date 2020-07-06.09:49:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Since you ask, here is a extended summary of namespaces. There is one built-in namespace.  There is one global namespace for each module, which is also the local namespace for top level code in that module.  There is one local namespace for each class and function.  There is one nonlocal namespace for each nested function.  "At any time during execution" (the beginning of the doc sentence targeted by this issue), there are 3 or maybe 4 namespaces accessible with simple undotted names. 

Module global and class local namespaces, including nested classes, are accessible from without the object with dotted names.  There are rules for class and method code about access to superclass namespaces.  Function locals are not necessarily accessible with standard python code, but at least in cpython, local names can be accessed via code objects.  Default parameter values and current nonlocal values, when set, can be accessed via function objects.  Dotted names are discussed elsewhere in the tutorial, while function and code object introspection is out of scope there.  (And off topic for this issue ;-).
Date User Action Args
2020-07-06 09:49:06terry.reedysetrecipients: + terry.reedy, brett.cannon, ezio.melotti, docs@python, veky, Hibou57, Roscoe R. Higgins, Mariatta, cheryl.sabella, miss-islington, nanjekyejoannah
2020-07-06 09:49:06terry.reedysetmessageid: <>
2020-07-06 09:49:06terry.reedylinkissue26205 messages
2020-07-06 09:49:06terry.reedycreate