Rémi Lapeyre <[email protected]> added the comment:
I see your point.
On the other hand, a new parameter would also increase the complexity for the
user.
Maybe it should not be seen as re-ordering but just a "zipping" them correctly:
@dataclass
class Parent:
i: int
j: int = 0
@dataclass
class Child(Parent):
k: int
l: int = 1
The "naive" to define Child's __index__ is:
__index__(self, i: int, j: int = 0, k: int, l: int = 1):
but wouldn't this make sense (given that it is previsible and deterministic)?
__index__(self, i: int, k: int, j: int = 0, l: int = 1):
----------
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue36077>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
