I don't think it matters so much whether you are stacking two decorators or a single decorator, but would an @add_unsafe_hash decorator be useful for anything *except* data classes? If not, then there's no point in having a *second* decorator that can *only* modify the first one - particularly considering @dataclass actually takes arguments.
On 02/05/2018 02:12 PM, Guido van Rossum wrote: > Yes, that's what I meant -- "afterwards" meaning after the @dataclass > decorator is applied. > > On Mon, Feb 5, 2018 at 11:09 AM, Kirill Balunov <kirillbalu...@gmail.com> > wrote: > >> >> 2018-02-05 20:47 GMT+03:00 Guido van Rossum <gu...@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 >> > > > > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/paul%40ganssle.io >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
