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, lemburg, p-ganssle
Date 2019-02-15.14:28:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550240916.35.0.451510247621.issue36004@roundup.psfhosted.org>
In-reply-to
Content
Datetime has many methods that "serializes" an instance to some other format - toordinal, timestamp, isoformat, etc. Most methods that "serialize" a datetime have a corresponding method that "deserializes" that method, or another way to reverse the operation:

- strftime / strptime
- timestamp / fromtimestamp
- isoformat / fromisoformat
- toordinal / fromordinal
- timetuple / datetime(*thetuple[0:6])

However, as I found out when implementing `dateutil.parser.isoparse`, there is no simple way to invert `isocalendar()`.

I have an implementation as part of dateutil.parser.isoparse:

https://github.com/dateutil/dateutil/blob/master/dateutil/parser/isoparser.py#L297

If there are no objections, I'd like to add an implementation in CPython itself. Thinking the name should be `fromisocalendar`.
History
Date User Action Args
2019-02-15 14:28:36p-gansslesetrecipients: + p-ganssle, lemburg, belopolsky
2019-02-15 14:28:36p-gansslesetmessageid: <1550240916.35.0.451510247621.issue36004@roundup.psfhosted.org>
2019-02-15 14:28:36p-gansslelinkissue36004 messages
2019-02-15 14:28:36p-gansslecreate