[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
R. David Murray
report at bugs.python.org
Fri Mar 7 16:12:54 CET 2014
R. David Murray added the comment:
> 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?
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13936>
_______________________________________
More information about the Python-bugs-list
mailing list