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 docs@python, maggyero, steven.daprano, terry.reedy
Date 2020-09-17.07:18:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The main issue I have with the existing doc is its use of 'top-level' to mean the main, initial, startup module that first executes the user code for a python 'program'.  We routinely use 'top-level' instead for the global scope of a module.  Example:, 'qualified name' entry, line 2: "For top-level functions and classes, ..."  Within '__main__', some code is top-level, but class and function bodies are not.

But this does not have to be part of this PR.
Date User Action Args
2020-09-17 07:18:50terry.reedysetrecipients: + terry.reedy, steven.daprano, docs@python, maggyero
2020-09-17 07:18:50terry.reedysetmessageid: <>
2020-09-17 07:18:50terry.reedylinkissue39452 messages
2020-09-17 07:18:49terry.reedycreate