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 tim.peters
Recipients belopolsky, berker.peksag, bmispelon, corona10, p-ganssle, rhettinger, serhiy.storchaka, taleinat, tim.peters, vstinner
Date 2019-09-13.17:26:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1568395571.85.0.184833107628.issue24416@roundup.psfhosted.org>
In-reply-to
Content
I agree with Raymond here:  using collections.namedtuple is fine in the pure Python version.  Since Raymond checked in doc changes to purge the phrase "struct sequences" (thanks again for that!), it's consistent with everything else now for the new datetime docs to say that this function returns a "named tuple" (the docs are now clear that there may be more than one implementation of such a thing, and that the only things you can _rely_ on are that they support named element access in addition to tuple methods).
History
Date User Action Args
2019-09-13 17:26:11tim.peterssetrecipients: + tim.peters, rhettinger, belopolsky, vstinner, taleinat, berker.peksag, serhiy.storchaka, bmispelon, p-ganssle, corona10
2019-09-13 17:26:11tim.peterssetmessageid: <1568395571.85.0.184833107628.issue24416@roundup.psfhosted.org>
2019-09-13 17:26:11tim.peterslinkissue24416 messages
2019-09-13 17:26:11tim.peterscreate