Message368491
Thanks David for the report and the draft PR (which helped me validate my thinking on the matter). In PR 20015, I've included additional tests. I've also re-written the compatibility functions to rely on the main `__iter__` override.
Another situation that's likely to be incompatible is pickleability. Is that important?
I'm tempted to make deprecated the use of `uname_result` for anything other than attribute access (maybe with the ability to cast to a tuple, i.e. `tuple(res)`). The problem with namedtuples is that although they provide backward-compatibility for legacy behavior which returned tuples, they also bring that legacy as debt. By deprecating "access by index", that would constrain the interface to two basic usages: attribute access and `iter()` of all values. |
|
| Date |
User |
Action |
Args |
| 2020-05-09 00:26:36 | jaraco | set | recipients:
+ jaraco, lemburg, tucked |
| 2020-05-09 00:26:35 | jaraco | set | messageid: <[email protected]> |
| 2020-05-09 00:26:35 | jaraco | link | issue40570 messages |
| 2020-05-09 00:26:34 | jaraco | create | |
|