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, docs@python, jerrykramskoy, louielu, matrixise, p-ganssle, steve.dower, tim.peters
Date 2019-03-28.13:52:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Can we change the title of this to something like, "Add example of platform-specific support for negative timestamps to the time documentation"?

That might be a bit wordy, but as it is now, this looks like it's reporting a bug in dateutil, which is not part of the standard library, which may be confusing people looking for something to solve.

As for the meat of the documentation change, I think we can adapt the wording from `datetime.fromtimestamp`, which actually has a very similar example called out:

> fromtimestamp() may raise OverflowError, if the timestamp is out of the range of values supported by the platform C localtime() or gmtime() functions, and OSError on localtime() or gmtime() failure. It’s common for this to be restricted to years in 1970 through 2038.
Date User Action Args
2019-03-28 13:52:04p-gansslesetrecipients: + p-ganssle, tim.peters, belopolsky, docs@python, steve.dower, matrixise, louielu, jerrykramskoy
2019-03-28 13:52:04p-gansslesetmessageid: <>
2019-03-28 13:52:04p-gansslelinkissue31327 messages
2019-03-28 13:52:04p-gansslecreate