➜

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 Alexander.Belopolsky, amaury.forgeotdarc, eric.araujo, fredrikj, jess.austin, jribbens, mark.dickinson, r.david.murray, tleeuwenburg@gmail.com, vstinner, webograph
Date 2010-04-19.20:53:49
SpamBayes Score 0.00038978006
Marked as misclassified No
Message-id <1271710430.92.0.745635834394.issue2706@psf.upfronthosting.co.za>
In-reply-to
Content 
Hmm.  Having timedelta // int work is *really* peculiar, since it can only be made sense of with reference to some implicit particular chosen unit of time;  in this case, that unit of time is apparently microseconds, as far as I can tell.

Surely there aren't any applications for timedelta // int?!  The operation just doesn't make dimensional sense, since it involves taking floor of a timedelta.

I vote -3.2 minutes on extending this craziness by adding timedelta % int or divmod(timedelta, int).
History
Date User Action Args
2010-04-19 20:53:51mark.dickinsonsetrecipients: + mark.dickinson, jribbens, amaury.forgeotdarc, vstinner, jess.austin, fredrikj, webograph, eric.araujo, r.david.murray, tleeuwenburg@gmail.com, Alexander.Belopolsky
2010-04-19 20:53:50mark.dickinsonsetmessageid: <1271710430.92.0.745635834394.issue2706@psf.upfronthosting.co.za>
2010-04-19 20:53:49mark.dickinsonlinkissue2706 messages
2010-04-19 20:53:49mark.dickinsoncreate