➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2008-03-17 16:34 by brett.cannon, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg63667 - (view) | Author: Brett Cannon (brett.cannon) *  |
Date: 2008-03-17 16:34 | |
structseq and namedtuple should end up with a uniformed API. |
|||
| msg63763 - (view) | Author: Raymond Hettinger (rhettinger) * |
Date: 2008-03-17 20:36 | |
Closing as a duplicate of issue 1820. I had been working on this, but there are limits to it. The constructors are completely different so not all of the API can be synced. The __repr__ method is already synced-up. All that is still needed is _asdict(), _fields, and _replace(). The important parts like the __repr__, matching most of the tuple API, and attribute access are already done. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:31 | admin | set | github: 46576 |
| 2008-03-17 20:36:00 | rhettinger | set | status: open -> closed resolution: duplicate messages: + msg63763 nosy: + rhettinger title: Unify structseq and namedtuple's API -> Make structseq's API look more like a nametuple. |
| 2008-03-17 20:08:57 | brett.cannon | set | priority: release blocker -> critical |
| 2008-03-17 16:34:27 | brett.cannon | create | |