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 ronaldoussoren
Recipients christian.heimes, ned.deily, ronaldoussoren, shields-fn
Date 2020-06-23.11:14:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1592910847.17.0.146313399182.issue41083@roundup.psfhosted.org>
In-reply-to
Content
Year 0 does exist in ISO 8601 though, but that wouldn't help us here as year 0 in that standard is year 1 BCE which is not representable in Python's datetime module.

I'm not sure what we can do about this. The best we could do with plistlib is probably to add an option to either set unrepresentable dates to None or represent those dates as strings.

A more comprehensive fix is to change datetime to be able to represent these dates, but that's a much larger change that likely requires a PEP.
History
Date User Action Args
2020-06-23 11:14:07ronaldoussorensetrecipients: + ronaldoussoren, christian.heimes, ned.deily, shields-fn
2020-06-23 11:14:07ronaldoussorensetmessageid: <1592910847.17.0.146313399182.issue41083@roundup.psfhosted.org>
2020-06-23 11:14:07ronaldoussorenlinkissue41083 messages
2020-06-23 11:14:07ronaldoussorencreate