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 srittau
Recipients amaury.forgeotdarc, belopolsky, brett.cannon, catlee, erik.stephens, guettli, jribbens, lemburg, pitrou, skip.montanaro, srittau, steve.roberts, tim.peters, tomster, vstinner
Date 2008-12-15.13:14:11
SpamBayes Score 4.08118e-07
Marked as misclassified No
Message-id <>
Leap second handling is usually configurable. Default on Debian Linux
(but similar on RHEL and SuSE):

>>> int(date(1994,1,1).strftime("%s")) - int(date(1993,1,1).strftime("%s"))

After doing "cp /usr/share/zoneinfo/right/Europe/Berlin /etc/localtime":

>>> int(date(1994,1,1).strftime("%s")) - int(date(1993,1,1).strftime("%s"))

Also, NTP servers usually get this right. I don't think, Python should
promote a wrong date handling by default, even if it's convenient.
Date User Action Args
2008-12-15 13:14:12srittausetrecipients: + srittau, lemburg, tim.peters, skip.montanaro, brett.cannon, jribbens, guettli, amaury.forgeotdarc, belopolsky, pitrou, catlee, vstinner, tomster, erik.stephens, steve.roberts
2008-12-15 13:14:12srittausetmessageid: <>
2008-12-15 13:14:11srittaulinkissue1673409 messages
2008-12-15 13:14:11srittaucreate