➜

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 Dave Johansen
Recipients Dave Johansen, belopolsky, vstinner
Date 2017-08-16.22:02:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1502920950.69.0.0385930122319.issue31212@psf.upfronthosting.co.za>
In-reply-to
Content 
The use case was parsing user input of ISO 8601 date strings and converting them to UNIX epochs.  The input "0001-01-01T00:00:00" is valid, parses to a valid `datetime` and it seems like a reasonable expectation that all of the functions should work on a valid `datetime` (especially when they worked in earlier versions of Python).
History
Date User Action Args
2017-08-16 22:02:30Dave Johansensetrecipients: + Dave Johansen, belopolsky, vstinner
2017-08-16 22:02:30Dave Johansensetmessageid: <1502920950.69.0.0385930122319.issue31212@psf.upfronthosting.co.za>
2017-08-16 22:02:30Dave Johansenlinkissue31212 messages
2017-08-16 22:02:30Dave Johansencreate