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.10:03:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Besides the sentence now revised, the initial post referenced confusion with 'middle scope' in "If a name is declared global, then all references and assignments go directly to the middle scope containing the module's global names."

This has not been directly discussed that I could find, but it seems inappropriate both at toplevel, where globals = locals, and in nested functions, where nonlocals are also 'middle'.  Maybe replace "the middle scope containing the module's global names" with "the module's global namespace".  The rest of this paragraph and the next could be reviewed.
Date User Action Args
2020-07-06 10:03:00terry.reedysetrecipients: + terry.reedy, brett.cannon, ezio.melotti, docs@python, veky, Hibou57, Roscoe R. Higgins, Mariatta, cheryl.sabella, miss-islington, nanjekyejoannah
2020-07-06 10:03:00terry.reedysetmessageid: <>
2020-07-06 10:03:00terry.reedylinkissue26205 messages
2020-07-06 10:03:00terry.reedycreate