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:08:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
When I rejected that approach previously, it hadn't occurred to me yet that the write-through proxy could write through to both the frame state *and* the regular dynamic snapshot returned by locals().

The current design came from asking myself "What if the proxied reads always came from the snapshot, just like they do now, but writes went to *both* places?".

So far I haven't found any fundamental problems with the approach, but I also haven't implemented it yet - I've only read through all the places in the code where I think I'm going to have to make changes in order to get it to work.
Date User Action Args
2017-10-22 15:08:52ncoghlansetrecipients: + ncoghlan, arigo, belopolsky, benjamin.peterson, njs, xdegaye, Mark.Shannon, yselivanov, xgdomingo
2017-10-22 15:08:52ncoghlansetmessageid: <>
2017-10-22 15:08:52ncoghlanlinkissue30744 messages
2017-10-22 15:08:51ncoghlancreate