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 skrah
Recipients Camion, levkivskyi, r.david.murray, skrah
Date 2017-12-19.09:45:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513676732.2.0.213398074469.issue32361@psf.upfronthosting.co.za>
In-reply-to
Content
> Does it makes sense to have the presence of "global a" in g, block all possibility for h, to access it's grand parent's a ?

From the perspective of ML-style languages with pure lexical scoping, no, it does not make sense.


But Python started with C-like simple name spaces, then nested functions and 'nonlocal' were added.


I think the answer (as usual) is that people may rely on the established convention and that it is no problem in practice.
History
Date User Action Args
2017-12-19 09:45:32skrahsetrecipients: + skrah, r.david.murray, levkivskyi, Camion
2017-12-19 09:45:32skrahsetmessageid: <1513676732.2.0.213398074469.issue32361@psf.upfronthosting.co.za>
2017-12-19 09:45:32skrahlinkissue32361 messages
2017-12-19 09:45:32skrahcreate