Paul Ganssle <p.gans...@gmail.com> added the comment:

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.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue42070>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to