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 r.david.murray
Recipients Amber.Yust, Andreas.Pelme, Hanxue.Lee, Lakin.Wecker, alex, belopolsky, cvrebert, dstufft, eric.araujo, ethan.furman, georg.brandl, gwrtheyrn, lemburg, ncoghlan, pitrou, r.david.murray, shai, skip.montanaro, tim.peters, yselivanov
Date 2014-03-07.15:12:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> it wasn't an accident, it was designed so modulo arithmetic could reasonably be implemented for time() objects (which hasn't been demanded or implemented since the datetime module was created)

Ah, interesting.  I just wrote a program last month where I was baffled that time didn't support arithmetic, and had to dodge painfully through datetime instances to do the arithmetic.  I asked about it on IRC and someone said it was because arithmetic on times was ambiguous because of timezones, and I just accepted that rather than wonder why it hadn't been implemented.

Otherwise I'm pretty sympathetic to the RFE, but I'd really like time arithmetic to work, so I guess I'd have to be -1 in that case, wouldn't I?
Date User Action Args
2014-03-07 15:12:54r.david.murraysetrecipients: + r.david.murray, lemburg, tim.peters, skip.montanaro, georg.brandl, ncoghlan, belopolsky, pitrou, eric.araujo, alex, cvrebert, ethan.furman, gwrtheyrn, Lakin.Wecker, yselivanov, shai, dstufft, Andreas.Pelme, Amber.Yust, Hanxue.Lee
2014-03-07 15:12:54r.david.murraysetmessageid: <>
2014-03-07 15:12:54r.david.murraylinkissue13936 messages
2014-03-07 15:12:53r.david.murraycreate