> Does this mean that there are circumstances where monotonic will work for a > while, but then fail?
No. time.monotonic() always work or always fail. If monotonic() failed, steady() doesn't call it again. > Otherwise, we would only need to check monotonic once, when the time module > is first loaded, rather than every time it is called. Instead of the above: > > # global to the time module > try: > monotonic() > except (NameError, OSError): > steady = time > else: > steady = monotonic I implemented steady differently to avoid the need of calling monotonic at Python startup. Calling monotonic at startup would be an extra useless system call. 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
