> On Dec 21, 2017, at 3:21 PM, Gregory P. Smith <g...@krypto.org> wrote: > > It seems a suggested use is "from dataclasses import dataclass" > > But people are already familiar with "from collections import namedtuple" > which suggests to me that "from collections import dataclass" would be a more > natural sounding API addition.
This might make sense if it were a single self contained function. But dataclasses are their own little ecosystem that warrants its own module namespace: >>> import dataclasses >>> dataclasses.__all__ ['dataclass', 'field', 'FrozenInstanceError', 'InitVar', 'fields', 'asdict', 'astuple', 'make_dataclass', 'replace'] Also, remember that dataclasses have a dual role as a data holder (which is collection-like) and as a generator of boilerplate code (which is more like functools.total_ordering). I support Eric's decision to make this a separate module. Raymond _______________________________________________ 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
