[TIm] > Note that this doesn't help for mixed-type time or timedelta comparison: > datetime's time and timedelta objects don't have timetuple methods > themselves, and their comparison implementations still raise TypeError > whenever they don't recognize the other comparand's type (this > is needed to prevent comparison against objects of arbitrary types from > falling back to the default comparison of object addresses). [M.-A. Lemburg] > Why not add them (setting the date parts to None) ? Because they're of no use, and at least timedelta.timetuple() wouldn't even make hallucinogenic sense (a timetuple is in units of days, seconds and microseconds).
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4