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
There are no provisions right now to separate the MutableMapping method names (copy, keys, etc...) from context-variable keys - (the current behavior is even undefined, as in "I don't know what would happen if one is to use these keys" .
The suggestion is to separate a reserved attribute list as a class attribute (with the _et_ prefix, which should be reserved anyway) and give some special treatment to those. They colliding names should then just work on ContextMap instances, and maybe error with AttributeError on ContextLocal distances (there are no public methods there yet, but maybe copy_context and run should be reserved for future implementation of the functionality available in contextvars.Context)
The text was updated successfully, but these errors were encountered:
There are no provisions right now to separate the MutableMapping method names (
copy
,keys
, etc...) from context-variable keys - (the current behavior is even undefined, as in "I don't know what would happen if one is to use these keys" .The suggestion is to separate a reserved attribute list as a class attribute (with the
_et_
prefix, which should be reserved anyway) and give some special treatment to those. They colliding names should then just work onContextMap
instances, and maybe error withAttributeError
onContextLocal
distances (there are no public methods there yet, but maybecopy_context
andrun
should be reserved for future implementation of the functionality available in contextvars.Context)The text was updated successfully, but these errors were encountered: