Changes by Stefan Krah stefan-use...@bytereef.org:
--
resolution: - duplicate
stage: - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20230
___
Changes by Stefan Krah stefan-use...@bytereef.org:
--
superseder: - Enhance Object/structseq.c to match namedtuple and tuple
api
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20230
Changes by Stefan Krah stefan-use...@bytereef.org:
--
nosy: +skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20230
___
___
Python-bugs-list
New submission from Andrew Barnert:
A PyStructSequence type doesn't expose its field names in any way to Python
code (except indirectly, via the repr, which you could parse if you really
wanted to…).
The docs claim that Struct sequence objects are the C equivalent of
namedtuple() objects, so
Changes by Meador Inge mead...@gmail.com:
--
nosy: +meador.inge
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20230
___
___
Python-bugs-list
Andrew Barnert added the comment:
After more searching (I should have searched on structseq instead of
PyStructSequence…), this might be a dup of #1820. If so, apologies.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20230
Changes by Ethan Furman et...@stoneleaf.us:
--
nosy: +ethan.furman
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20230
___
___
Python-bugs-list
Changes by Yury Selivanov yseliva...@gmail.com:
--
nosy: +yselivanov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20230
___
___
Python-bugs-list
Changes by Yury Selivanov yseliva...@gmail.com:
--
components: +Interpreter Core, Library (Lib)
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20230
___
