[Python-Dev] Dataclasses, frozen and __post_init__
Chris Barker - NOAA Federal
chris.barker at noaa.gov
Mon Feb 19 23:16:00 EST 2018
But how?
Well, I hadn’t thought that far ;-)
But it would make frozen an instance level property, rather than a
class-level one — some instances would be frozen, some not.
Which would be kinda compatible with the idea of hashability being a
property of values, rather than type. Frozen-ness would also be a property
of values.
But it would require a flag, and a bunch of logic overhead, which could get
pretty ugly so maybe not worth it.
-CHB
On Mon, Feb 19, 2018 at 5:06 PM, Chris Barker - NOAA Federal <
chris.barker at noaa.gov> wrote:
> If I have this right, on the discussion about frozen and hash, a use
> case was brought up for taking a few steps to create an instance (and
> thus wanting it not frozen) and then wanting it hashable.
>
> Which pointed to the idea of a “ freeze this from now on” method.
>
> This seems another use case — maybe it would be helpful to be able to
> freeze an instance after creation for multiple use-cases?
>
> -CHB
>
--
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20180219/8053cddc/attachment.html>
More information about the Python-Dev
mailing list