Author p-ganssle
Recipients belopolsky, msimpasona, p-ganssle
Date 2020-10-18.20:53:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1603054418.27.0.242561079588.issue42070@roundup.psfhosted.org>
In-reply-to
Content
That's a reasonable enough objection, though what use case do you have for storing the IsocalendarDate object? The main reason we switched to using a named tuple like this was because the vast majority of uses of `isocalendar()` that I saw were people doing stuff like `dt.isocalendar()[0]`, rather than destructuring the tuple or accessing more than one element from the result.

It seems to me that if you are using a pickle for a cache, you'd either pickle the `datetime` itself (and call `.isocalendar()` in the process that has read from the cache already), or you'd store one or more of the fields directly on the object that you are caching.

A real life use case for this would help.
History
Date User Action Args
2020-10-18 20:53:38p-gansslesetrecipients: + p-ganssle, belopolsky, msimpasona
2020-10-18 20:53:38p-gansslesetmessageid: <1603054418.27.0.242561079588.issue42070@roundup.psfhosted.org>
2020-10-18 20:53:38p-gansslelinkissue42070 messages
2020-10-18 20:53:38p-gansslecreate