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 martin.panter
Recipients BreamoreBoy, belopolsky, flox, martin.panter, python-dev, vstinner
Date 2016-07-14.05:41:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If you enable GCC’s -ftrapv option, the subtraction overflow triggers an abort. Alexander’s patch works around the problem for asctime(), but the problem still exists in other cases, such as:

>>> time.mktime((-2**31 + 1899, *(0,) * 8))
Aborted (core dumped)
[Exit 134]

Attaching a version of the patch without the conflicting whitespace changes.

Why does Python even need to support such extreme time values? It would seem much simpler to raise an exception.
Date User Action Args
2016-07-14 05:41:49martin.pantersetrecipients: + martin.panter, belopolsky, vstinner, flox, BreamoreBoy, python-dev
2016-07-14 05:41:49martin.pantersetmessageid: <>
2016-07-14 05:41:49martin.panterlinkissue13312 messages
2016-07-14 05:41:49martin.pantercreate