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 amaury.forgeotdarc, belopolsky, jribbens, mark.dickinson, vstinner, webograph
Date 2008-11-15.10:08:07
SpamBayes Score 6.09963e-07
Marked as misclassified No
Message-id <>
> timedelta / <float or int> should be disallowed in true division mode.

I don't understand this;  why should the division mode affect
division operations involving timedeltas at all?  The meaning
of "/" is unaffected by the division mode for float/float or
float/int;  why should timedeltas be any different?

I vote +1 for timedelta/timedelta and timedelta/float (regardless
of division mode).  timedelta / timedelta is the one obvious way
to find out 'how many A's in B', and the one that it's natural
to try first, before looking for (timedelta -> float) conversion
Date User Action Args
2008-11-15 10:08:09mark.dickinsonsetrecipients: + mark.dickinson, jribbens, amaury.forgeotdarc, belopolsky, vstinner, webograph
2008-11-15 10:08:08mark.dickinsonsetmessageid: <>
2008-11-15 10:08:07mark.dickinsonlinkissue2706 messages
2008-11-15 10:08:07mark.dickinsoncreate