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-07.05:21:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1567833663.74.0.885086683398.issue24416@roundup.psfhosted.org>
In-reply-to
Content
I favor making this a structseq, primarily based on Paul's attempt to find actual use cases, which showed that named member access would be most useful most often.  I have no intuition for that myself, because while I wrote the original functions here, I've never used them and never will ;-)  But if I ever did, I'd probably want the ISO week number, and would appreciate not having to remember which meaningless index means "week".

Don't care about moving pickles to older versions.

Don't care about the putative speed hit - it's still measured in nanoseconds, so can still create over a million per second.  In apps with a large number of dates, they're typically not _calculated_, but read up from a relatively snail-like database or network connection.  I doubt anyone would notice if `.isocalendar()` got 10x slower.

Note:  I'm unassigning myself, because I have nothing else to say :-)
History
Date User Action Args
2019-09-07 05:21:03tim.peterssetrecipients: + tim.peters, rhettinger, belopolsky, vstinner, taleinat, berker.peksag, serhiy.storchaka, bmispelon, p-ganssle, corona10
2019-09-07 05:21:03tim.peterssetmessageid: <1567833663.74.0.885086683398.issue24416@roundup.psfhosted.org>
2019-09-07 05:21:03tim.peterslinkissue24416 messages
2019-09-07 05:21:03tim.peterscreate