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 ncoghlan
Recipients Mark.Shannon, arigo, belopolsky, benjamin.peterson, ncoghlan, njs, xdegaye, xgdomingo, yselivanov
Date 2017-10-22.15:03:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1508684602.63.0.213398074469.issue30744@psf.upfronthosting.co.za>
In-reply-to
Content
No, as locals() never returns the write-through proxy in the latest version of the PEP - it only ever returns the dynamic snapshot namespace (retrieving it from the proxy if necessary).

To get access to the write-through proxy in Python level code, you have to access frame.f_locals directly (which trace functions will do by necessity, since that's the only way they have to get at the function locals).
History
Date User Action Args
2017-10-22 15:03:22ncoghlansetrecipients: + ncoghlan, arigo, belopolsky, benjamin.peterson, njs, xdegaye, Mark.Shannon, yselivanov, xgdomingo
2017-10-22 15:03:22ncoghlansetmessageid: <1508684602.63.0.213398074469.issue30744@psf.upfronthosting.co.za>
2017-10-22 15:03:22ncoghlanlinkissue30744 messages
2017-10-22 15:03:22ncoghlancreate