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 josh.r
Recipients BreamoreBoy, Christian.Tismer, barry, dilettant, eli.bendersky, eric.smith, gvanrossum, josh.r, ncoghlan, rhettinger, sbt
Date 2014-06-14.02:02:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I was already thinking of the same solution Christian.Tismer proposed before I reached his post. namedtuples seem cleaner if they naturally act as singletons, so (potentially whether or not pickling is involved) declaring a namedtuple with the same name and fields twice returns the same class. Removes the need to deal with module qualified names, and if pickle can be made to support it, the namedtuple class itself could be pickled uniquely in such a way that it could be recreated by someone else who didn't even have a local definition of the namedtuple, the module that defines it, etc.
Date User Action Args
2014-06-14 02:02:46josh.rsetrecipients: + josh.r, gvanrossum, barry, rhettinger, ncoghlan, eric.smith, eli.bendersky, BreamoreBoy, sbt, dilettant, Christian.Tismer
2014-06-14 02:02:46josh.rsetmessageid: <>
2014-06-14 02:02:46josh.rlinkissue17941 messages
2014-06-14 02:02:46josh.rcreate