Skip Montanaro <s...@pobox.com>: > There is a good reason that the internal units of timedelta objects > are days, seconds, and microseconds. They are well-defined outside of > a calendar context. > > So, I guess Roy is back to square one. He can always roll his own > timedelta subclass and give it a __str__ implementation...
If you don't want to mix the intricacies of calendars to datetime and timedelta, why use them? (Epoch) seconds do everything for you unambiguously. Yes, yes. The physicists ought to stop fricking around with leap seconds. They should declare a 3000-year moratorium on leap seconds. Marko -- https://mail.python.org/mailman/listinfo/python-list
