➜

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 belopolsky
Recipients Arfrever, barry, belopolsky, lemburg, pitrou, thomir, veebers
Date 2014-10-15.01:01:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1413334883.56.0.726654771527.issue22627@psf.upfronthosting.co.za>
In-reply-to
Content 
Antoine,

I don't think the behavior that you have shown is a bug in strict sense.

On my Mac, I get

$ python mkbug.py breakme
1396702800.0
1396702800.0

but on Linux,

$ python mkbug.py breakme
1396706400.0
1396702800.0

The problem here is that time.mktime((2014, 4, 6, 2, 0, 0, -1, -1, -1))
is undefined  and both 1396706400 and 1396702800 timestamps are valid guesses for what 2014-04-06T02 was in NZ: 

$ TZ=NZ date -d @1396706400
Sun Apr  6 02:00:00 NZST 2014
$ TZ=NZ date -d @1396702800
Sun Apr  6 02:00:00 NZDT 2014

It is unfortunate that Linux C library (glibc?) makes different guess at different time, but I don't think this violates any applicable standards.
History
Date User Action Args
2014-10-15 01:01:23belopolskysetrecipients: + belopolsky, lemburg, barry, pitrou, Arfrever, thomir, veebers
2014-10-15 01:01:23belopolskysetmessageid: <1413334883.56.0.726654771527.issue22627@psf.upfronthosting.co.za>
2014-10-15 01:01:23belopolskylinkissue22627 messages
2014-10-15 01:01:23belopolskycreate