You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once python/peps#3845 lands PEP 667 will contain such a description, but the main docs should at least cover the key behaviours:
new instance on every attribute access
two proxies with the same keys and values will still be unequal if they refer to different frames
extra keys can be stored and are stored on the frame itself so they're shared across all proxies for the same frame
keys corresponding to local variables can't be deleted
.copy() (and any other API that produces a new container) returns a regular dict instance
Suggested location would be as a new 4th subsection under the frame objects section linked above. A "see also" from that new subsection back to PEP 667 would also be a useful addition.
I would like to work on this issue. I have reviewed the requirements and drafted the new subsection under the Frame Objects section in Doc/reference/datamodel.rst covering the 5 key proxy behaviors you listed, along with a seealso reference to PEP 667.
Activity
VimalN2005 commentedon Sep 10, 2026
Hi @ncoghlan,
I would like to work on this issue. I have reviewed the requirements and drafted the new subsection under the Frame Objects section in
Doc/reference/datamodel.rstcovering the 5 key proxy behaviors you listed, along with aseealsoreference to PEP 667.May I go ahead and open a pull request for this?