[Python-ideas] Revisiting Immutable Mappings
szport at gmail.com
Thu Oct 11 05:18:52 EDT 2018
May be the following simple prototype of frozendict could be useful?
return RuntimeError("frozendict is not mutable")
def __setitem__(self, key, val):
def setdefault(self, key, val=None):
def update(self, ob):
def popitem(self, ob):
def clear(self, ob):
def __delitem__(self, key):
return "frozendict(" + dict.__repr__(self)[1:-1] + ")"
return "frozendict(" + dict.__str__(self)[1:-1] + ")"
def fromkeys(self, keys, val=None):
return frozendict([(key,val) for key in keys])
среда, 10 октября 2018 г., 20:06:03 UTC+3 пользователь Philip Martin
> Hi, I first want to thank everyone in the community for the contributions
> over the years. I know the idea of a frozendict has been proposed before
> and rejected. I have a use case for a frozendict implementation that to my
> knowledge was not discussed during previous debates. My reasoning for a
> frozendict class stems from patterns I typically see arise when performing
> ETL or data integrations and conversions. I generally have used
> MappingProxyType as a way to set default mapping to a function or to set an
> empty mapping to a function. I've created a gist with an example use case:
> I've included an example of what code typically looks like when using
> MappingProxyType and what it could look like with a
> frozendict implementation. I believe this use case may also be
> under-reported in open source code as it often crops up when integrating
> third-party data sources, which at times can't be open sourced due to
> licensing issues. I would love to hear if anyone has used MappingProxyType
> in a similar manner, or if this use case could help warrant a frozendict in
> the standard library.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-ideas