>>> 2) get_clock_info returns a dict. Why not a namedtuple? >> >> Future flexibility. And there's no need for it to be a *tuple*. > > I haven't been paying attention to this discussion, so this isn't a > comment on any time functions specifically. > > But we generally use a namedtuple (or structseq) for things like > get_clock_info. For example, for sys.float_info there's no need for it > to be a tuple, and it can be extended in the future, yet it's a structseq.
Ok ok, I changed the is_adjusted flag to make it mandatory and I changed get_clock_info() to return a clock_info object. clock_info is a structseq. I didn't mention that clock_info can be read using an index because I really don't like the tuple-like API. Victor _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com