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 Camion
Recipients Camion, r.david.murray
Date 2017-12-19.03:57:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513655874.3.0.213398074469.issue32361@psf.upfronthosting.co.za>
In-reply-to
Content
Well, David, I'm convinced this behavior is "logical" and is not some "logic" flaw. My question is more about the fact that it is desirable and was intentionally designed that way,or if on the contrary no one thought it might happen that way and it's not what was wished.

I understand that it might be a problem to link to a global (global a), a variable (h's a) which was declared in a non-global way, but is makes sense to have the presence of "global a" in g, block all possibility for h, to access it's grand parent's a.

In all case, I believe this should at lease be clearly documented in (or in relation with) PEP 3104 to make sure it has been decided that way, or else it will look like a design hole.
History
Date User Action Args
2017-12-19 03:57:54Camionsetrecipients: + Camion, r.david.murray
2017-12-19 03:57:54Camionsetmessageid: <1513655874.3.0.213398074469.issue32361@psf.upfronthosting.co.za>
2017-12-19 03:57:54Camionlinkissue32361 messages
2017-12-19 03:57:53Camioncreate