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 mark.dickinson
Recipients belopolsky, exarkun, lemburg, madison.may, mark.dickinson, pitrou
Date 2013-08-03.16:36:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375547778.47.0.626883478405.issue18629@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure I see a use-case for timedelta // int at all.  To make sense of that, you first need some way to make sense of floor(timedelta), and as you say it's not clear what that should mean:  number of seconds?  number of days?  Either of those would seem more natural than number of microseconds, though.

timedelta // timedelta and timedelta / int on the other hand have an obvious meaning.
History
Date User Action Args
2013-08-03 16:36:18mark.dickinsonsetrecipients: + mark.dickinson, lemburg, exarkun, belopolsky, pitrou, madison.may
2013-08-03 16:36:18mark.dickinsonsetmessageid: <1375547778.47.0.626883478405.issue18629@psf.upfronthosting.co.za>
2013-08-03 16:36:18mark.dickinsonlinkissue18629 messages
2013-08-03 16:36:18mark.dickinsoncreate