Message357855
I've supported people hitting this issue before (see https://stackoverflow.com/a/53085935/100297, where I used a series of mixin classes to make use of the changing MRO when the mixins share base classes, to enforce a field order from inherited classes.
I'd be very much in favour of dataclasses using the attrs approach to field order: any field named in a base class *moves to the end*, so you can 'insert' your own fields by repeating parent fields that need to come later:
@attr.s(auto_attribs=True)
class Parent:
foo: str
bar: int
baz: bool = False
@attr.s(auto_attribs=True)
class Child(Parent):
spam: str
baz: bool = False
The above gives you a `Child(foo: str, bar: int, spam: str, baz: bool = False)` object, note that `baz` moved to the end of the arguments.
`dataclasses` currently doesn't do this, so it'd be a breaking change. |
|
Date |
User |
Action |
Args |
2019-12-05 15:44:44 | mjpieters | set | recipients:
+ mjpieters, eric.smith, remi.lapeyre, xtreak, Кирилл Чуркин, Epic_Wink, kgustyr, dplepage |
2019-12-05 15:44:44 | mjpieters | set | messageid: <1575560684.84.0.975321811892.issue36077@roundup.psfhosted.org> |
2019-12-05 15:44:44 | mjpieters | link | issue36077 messages |
2019-12-05 15:44:44 | mjpieters | create | |
|