Nick Coghlan added the comment: Structured data is just a shorthand way of referring to any Python object which is neither a number or a container and exhibits the default boolean behaviour where all instances are true.
The problem datetime.time is both that its current behaviour is internally incoherent (whether or not an aware time is false depends on the current timezone in unpredictable ways) and *also* inconsistent with its other behaviours that indicate it should be handled as a non-numeric value. Since it isn't a container either, standard conventions suggest that it should always be true. No *compelling* justifications for its atypical behaviour have been presented, just a case of Tim wanting to leave the door open to adding modular arithmetic directly on time instances. I suggest it makes far more sense to instead eliminate the quirky behaviour entirely and instead provide an easy way to convert a time to a timedelta relative to midnight. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13936> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com