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 xdegaye
Recipients Mark.Shannon, arigo, belopolsky, benjamin.peterson, ncoghlan, njs, xdegaye, xgdomingo, yselivanov
Date 2017-10-22.12:06:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Nick, in msg304388 you wrote "[allow] immediate write-through from trace functions". The latest iteration of PEP 558 says instead:

"tracing mode: the way the interpreter behaves when a trace hook has been registered..."

and also says:

"As long as the process remains in tracing mode, then __setitem__ and __delitem__ operations on the proxy will affect not only the dynamic snapshot, but also the corresponding fast local or cell reference on the underlying frame."

So write-through is allowed by the current PEP outside a trace function. Does not this change in some cases the behavior of code that updates the mapping returned by locals() when tracing mode is active from its standard behavior when there is no tracing ?
Date User Action Args
2017-10-22 12:06:24xdegayesetrecipients: + xdegaye, arigo, ncoghlan, belopolsky, benjamin.peterson, njs, Mark.Shannon, yselivanov, xgdomingo
2017-10-22 12:06:24xdegayesetmessageid: <>
2017-10-22 12:06:24xdegayelinkissue30744 messages
2017-10-22 12:06:23xdegayecreate