Message 211887 - Python tracker

➜

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	vstinner
Recipients	David.Edelsohn, python-dev, serhiy.storchaka, vstinner
Date	2014-02-21.22:57:07
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1393023428.22.0.326515507074.issue19748@psf.upfronthosting.co.za>
In-reply-to

Content
>>> time.mktime(time.localtime(-1)) Traceback (most recent call last): File "<stdin>", line 1, in <module> OverflowError: mktime argument out of range Oh yes, I now remember it. Sorry, it was 3 years ago: http://bugs.python.org/issue11188#msg128541 The problem is to detect invalid time tuple and support the timestamp value -1 (1 second before the UNIX epoch). I modified the test to skip mktime(localtime(-1)) test on AIX: changeset 00e94e454813. It would be nice to support this specific value, but I don't see how to implement it. It's maybe not possible.

>>> time.mktime(time.localtime(-1))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OverflowError: mktime argument out of range

Oh yes, I now remember it. Sorry, it was 3 years ago:
http://bugs.python.org/issue11188#msg128541

The problem is to detect invalid time tuple and support the timestamp value -1 (1 second before the UNIX epoch).

I modified the test to skip mktime(localtime(-1)) test on AIX: changeset 00e94e454813.

It would be nice to support this specific value, but I don't see how to implement it. It's maybe not possible.

History
Date	User	Action	Args
2014-02-21 22:57:08	vstinner	set	recipients: + vstinner, python-dev, serhiy.storchaka, David.Edelsohn
2014-02-21 22:57:08	vstinner	set	messageid: <1393023428.22.0.326515507074.issue19748@psf.upfronthosting.co.za>
2014-02-21 22:57:08	vstinner	link	issue19748 messages
2014-02-21 22:57:07	vstinner	create