New submission from Joe Jevnik:
I am working on implementing nameduple in C; I am almost there; however, on the
path of moving to full compatibility, I ran into a refcount issue somewhere.
Hopefully someone can help me work this out.
To describe the issue, When I run the collections tests I
Joe Jevnik added the comment:
Ideally, namedtuple is used to make your code cleaner, using magic indecies
is less clear than using a named index in a lot of cases. Because namedtuple is
mainly to make the code more readable, I don't think that it should have an
impact on the runtime
Joe Jevnik added the comment:
would the idea be to deprecate namedtuple in favor of a public structseq that
is exposed through collections, or change structseq to fit the namedtuple API?
--
___
Python tracker rep...@bugs.python.org
http
101 - 103 of 103 matches
Mail list logo