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 taleinat
Recipients berker.peksag, bmispelon, serhiy.storchaka, taleinat
Date 2015-06-09.19:51:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433879496.84.0.065645463415.issue24416@psf.upfronthosting.co.za>
In-reply-to
Content
> First, if pickle a namedtuple, it can't be unpickled in previous versions.

True, but I don't think Python goes as far as to promise that objects pickled in one version can be unpickled in previous versions.

> Second, namedtuple is slower and larger than tuple, so it shouldn't be used in memory or performance critical code.

True, but I doubt that such tuples are often used extensively in performance-critical areas of code. Also, code which does care about this could immediately convert these namedtuples into plain tuples, which would be backwards compatible.
History
Date User Action Args
2015-06-09 19:51:36taleinatsetrecipients: + taleinat, berker.peksag, serhiy.storchaka, bmispelon
2015-06-09 19:51:36taleinatsetmessageid: <1433879496.84.0.065645463415.issue24416@psf.upfronthosting.co.za>
2015-06-09 19:51:36taleinatlinkissue24416 messages
2015-06-09 19:51:36taleinatcreate