Author belopolsky
Recipients belopolsky, exarkun, lemburg, madison.may, mark.dickinson, pitrou, tim.peters
Date 2013-08-03.18:35:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375554951.53.0.451762339009.issue18629@psf.upfronthosting.co.za>
In-reply-to
Content
> I just want `timedelta / int` to do the same thing in Python 2.7
> with __future__.division as `timedelta / int` does in Python 3.

It other words you want to backport timedelta / int true division.  I am afraid it is 3-4 years too late for this request, but I will let others make a call.  Count me as -0.

I usually prefer explicit error over an obscure bug.  If we backport true division the -Qnew flag will be changing the meaning of timedelta / int very slightly: instead of rounding down it will round to nearest.  There are cases where this difference is important.  Furthemore, when people compare timedeltas in tests they rarely do it with precision tolerance.  If you have a good test coverage change from floor to true division may break your tests.

My recommendation is: replace timedelta / int with timedelta // int in your 2.x code.
History
Date User Action Args
2013-08-03 18:35:51belopolskysetrecipients: + belopolsky, lemburg, tim.peters, exarkun, mark.dickinson, pitrou, madison.may
2013-08-03 18:35:51belopolskysetmessageid: <1375554951.53.0.451762339009.issue18629@psf.upfronthosting.co.za>
2013-08-03 18:35:51belopolskylinkissue18629 messages
2013-08-03 18:35:51belopolskycreate