On Sun, Apr 8, 2012 at 3:42 AM, Antoine Pitrou <solip...@pitrou.net> wrote: > >> | I made the same suggestion earlier but I don't know that anyone did >> | anything with it. :-( It would be nice to know what clock sleep() uses >> | on each of the major platforms. >> >> I saw it but didn't know what I could do with it, or even if it can be >> found out in any very general sense. >> >> Looking at nanosleep(2) on a recent Linux system says: > > time.sleep() uses select(), not nanosleep(). > select() is not specified to use a particular clock. However, since it > takes a timeout rather than a deadline, it would be reasonable for it > to use a non-adjustable clock :-) > http://pubs.opengroup.org/onlinepubs/9699919799/functions/select.html
Still, my hope was to cut short a bunch of discussion by declaring that on every platform, one of the timers available should match the one used by sleep(), select() and the like -- assuming they all use the same timer underneath in a typical OS, even though (due to standardization at different times by different standards bodies) they aren't all specified the same. IOW "What's good enough for sleep() is good enough for user-implemented timeouts and scheduling." as a way to reach at least one decision for a platform with agreed-upon cross-platform characteristics that are useful. What to name it can't be decided this way, although I might put forward time.sleeptimer(). I personally have a need for one potentially different clock -- to measure short intervals for benchmarks and profiling. This might be called time.performancetimer()? -- --Guido van Rossum (python.org/~guido) _______________________________________________ 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
