Kirill Balunov kirillbalunov at gmail.com
Mon Feb 5 14:09:47 EST 2018

• Previous message (by thread): [Python-Dev] Dataclasses and correct hashability
• Next message (by thread): [Python-Dev] Dataclasses and correct hashability
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

2018-02-05 20:47 GMT+03:00 Guido van Rossum <guido at python.org>:

> If there's going to be an API for it, it should be in the class, not
> something that mutates the class afterwards.
>


I apologize and don't want to make unnecessary noise. But the already
selected design with decorator @dataclass implies that it will mutate
the freshly created class (which in its turn already limits some
possibilities), or I've missed something? If you meant that everything
should be defined in one place, then I basically understand your desire as
the least of two evils.

With kind regards,
-gdg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20180205/20cfb643/attachment.html>

---

• Previous message (by thread): [Python-Dev] Dataclasses and correct hashability
• Next message (by thread): [Python-Dev] Dataclasses and correct hashability
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list