Ronald Oussoren added the comment: datetime.time arithmetic cannot be timezone aware, as there is no associated date and hence you cannot possibly know if there it a DST transition.
I don't think this is a problem. Adding/removing time to a clock value has clear real-world semantics. Using the (naive) real world semantics is the best we can do and should generally give the expected answer. As to cross-timezone comparisons: time(0, tzinfo=est) - timedelta(hours=1) * 5 == time(0, tzinfo=utc) fails because the LHS of '==' is a time in a different timezone than the value on the RHS. That's expected and correct. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17267> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
