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.

Author pitrou
Recipients barry, jdwhitley, pitrou, rhettinger, rrenaud, skip.montanaro
Date 2009-03-08.13:33:50
SpamBayes Score 1.3981921e-08
Marked as misclassified No
Message-id <1236519232.33.0.923032773876.issue1818@psf.upfronthosting.co.za>
In-reply-to
Content
I don't understand why NamedTupleReader requires the fieldnames array
rather than the namedtuple class itself. If you could pass it the
namedtuple class, users could choose whatever namedtuple subclass with
whatever additional methods or behaviour suits them. It would make
NamedTupleReader more flexible and more useful.
History
Date User Action Args
2009-03-08 13:33:52pitrousetrecipients: + pitrou, skip.montanaro, barry, rhettinger, jdwhitley, rrenaud
2009-03-08 13:33:52pitrousetmessageid: <1236519232.33.0.923032773876.issue1818@psf.upfronthosting.co.za>
2009-03-08 13:33:50pitroulinkissue1818 messages
2009-03-08 13:33:50pitroucreate