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 p-ganssle
Recipients belopolsky, berker.peksag, bmispelon, corona10, p-ganssle, rhettinger, serhiy.storchaka, taleinat, tim.peters
Date 2020-05-16.14:17:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1589638628.25.0.635993216096.issue24416@roundup.psfhosted.org>
In-reply-to
Content
This is now merged, thanks for the debate and opinions offered everyone, and thanks to Dong-hee for the implementation!

The way we did the implementation, a pickle/unpickle cycle on the result of .isocalendar() will return a plain tuple. Despite the fact that I suggested it, I recognize that this is a /weird thing to do/, and I'm sorta banking on the fact that in all likelihood no one is relying on pickling and unpickling the result of .isocalendar() returning anything but a tuple (since, currently, that's already what it does, regardless of what the input type was).

I suppose we'll have to see if it causes problems in the beta period, and I'll keep a close eye on it.
History
Date User Action Args
2020-05-16 14:17:08p-gansslesetrecipients: + p-ganssle, tim.peters, rhettinger, belopolsky, taleinat, berker.peksag, serhiy.storchaka, bmispelon, corona10
2020-05-16 14:17:08p-gansslesetmessageid: <1589638628.25.0.635993216096.issue24416@roundup.psfhosted.org>
2020-05-16 14:17:08p-gansslelinkissue24416 messages
2020-05-16 14:17:08p-gansslecreate