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 belopolsky, exarkun, lemburg, madison.may, mark.dickinson, pitrou, tim.peters
Date 2013-08-03.18:19:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375553962.15.0.974596598789.issue18629@psf.upfronthosting.co.za>
In-reply-to
Content
There are two schools of thought here.  One school (MAL and Mark) thinks of durations as real number of seconds.  The other school (Tim and I) think of durations as integer number of resolution intervals.  This is why I and Tim before me resisted adding true division of timedelta by a number and multiplication of timedelta by a float.  Mark prevailed on that issue (see #1289118.)  His expertise in floating point computing certainly helped designing and implementing these operations correctly.  We still have a small quirk waiting to be ironed out (see #8860), but overall I am happy with the current state.

This said, the datetime module carries a long legacy of being a pure integer arithmetics in a funny variable-radix notation.  We can disagree on the utility of floor division as it is currently defined, but we cannot remove or change it in an incompatible way.
History
Date User Action Args
2013-08-03 18:19:22belopolskysetrecipients: + belopolsky, lemburg, tim.peters, exarkun, mark.dickinson, pitrou, madison.may
2013-08-03 18:19:22belopolskysetmessageid: <1375553962.15.0.974596598789.issue18629@psf.upfronthosting.co.za>
2013-08-03 18:19:22belopolskylinkissue18629 messages
2013-08-03 18:19:21belopolskycreate