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 jribbens
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.14:58:39
SpamBayes Score 3.70512e-05
Marked as misclassified No
Message-id <>
> A timedelta.toseconds method (or equivalent) makes no sense.
> The number of seconds in a day is not fixed (due to leap seconds) and
> relying on such a method would introduce subtle bugs.

You are misunderstanding what timedelta is. It is a fixed-length period
of time. It is stored as a number of (24x3600-second) days, seconds and
microseconds. There is no "start date" or "end date", so the concept of
leap seconds just does not apply.
Date User Action Args
2008-12-15 14:58:41jribbenssetrecipients: + jribbens, lemburg, tim.peters, skip.montanaro, brett.cannon, srittau, guettli, amaury.forgeotdarc, belopolsky, pitrou, catlee, vstinner, tomster, erik.stephens, steve.roberts
2008-12-15 14:58:41jribbenssetmessageid: <>
2008-12-15 14:58:40jribbenslinkissue1673409 messages
2008-12-15 14:58:39jribbenscreate