On 27/03/2012 20:18, Matt Joiner wrote:
Also monotonic should either not exist if it's not available, or always guarantee a (artificially) monotonic value.
What do you mean by "(artificially) monotonic value"? Should Python workaround OS bugs by always returning the maximum value of the clock?
Finding out that something is already known to not work shouldn't require a call and a faked OSError.
What do you mean? time.monotonic() is not implemented if the OS doesn't provide any monotonic clock (e.g. if clock_gettime(CLOCK_MONOTONIC) is missing on UNIX). OSError is only raised when the OS returns an error. There is no such "faked OSError".
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
