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 Zahari.Dim, docs@python, martin.panter, r.david.murray, terry.reedy
Date 2013-11-30.03:25:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385781954.76.0.439057459948.issue19737@psf.upfronthosting.co.za>
In-reply-to
Content
In my opinion, vague ideas like this one should go to python-ideas first.

I agree with David that globals() and locals() are separate issues. Since there have been and perhaps still are locals() doc issues, I will take this one to be about 'globals()'.

A 'symbol table' is a mapping between 'symbols' and 'values'. I presume such were originally implemented as a concrete list of pairs, but the term is now is an abstraction. In the Python context, I think 'namespace' would be a better word, but I would not make the change without getting other opinions, such as on python-ideas. 

The [...] that you omitted says "This is always the dictionary of the current module (...)." I cannot interpret 'is' to mean a copy. So I think "[concrete] dictionary represents [abstract] symbol table [namespace]" is fine.
History
Date User Action Args
2013-11-30 03:25:55terry.reedysetrecipients: + terry.reedy, r.david.murray, docs@python, martin.panter, Zahari.Dim
2013-11-30 03:25:54terry.reedysetmessageid: <1385781954.76.0.439057459948.issue19737@psf.upfronthosting.co.za>
2013-11-30 03:25:54terry.reedylinkissue19737 messages
2013-11-30 03:25:54terry.reedycreate