[issue31209] MappingProxyType can not be pickled

Alex Hayes added the comment: Closing issue - thanks rhettinger -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue31209] MappingProxyType can not be pickled

Raymond Hettinger added the comment: > So I guess my questions now are; > > 1. Should types.MappingProxyType be pickleable? > 2. Should there be some documentation about the intended use of > MappingProxyType? > > I imagine the answer to the first question is "no" given > how `__setstate__`

[issue31209] MappingProxyType can not be pickled

Alex Hayes added the comment: Some background. I'm not actually trying to pickle MappingProxyType, I'm using the schematics [1] library and recently it broke support for pickle [2] and the cause of that is because they are using MappingProxyType [3] internally (when they used to use dict).

[issue31209] MappingProxyType can not be pickled

Raymond Hettinger added the comment: What would be the point of pickling a MappingProxy? Do you have use case or is it just a curiosity? -- nosy: +rhettinger ___ Python tracker

[issue31209] MappingProxyType can not be pickled

New submission from Alex Hayes: I imagine that this is by design (likely because it can't be implemented) however I wanted to check if this was the case. Instances of types.MappingProxyType can't be pickled. For example; ``` import pickle from types import MappingProxyType eggs =