On 2012-04-03, at 8:33 PM, Steven D'Aprano wrote: > 1) the os module should expose lightweight wrappers around whatever clocks > the operating system provides;
+1. That should make it flexible enough to those who really need it. > 2) the time module should NOT provide any further clocks other than the > existing time() and clock() functions (but see point 4 below); > > 3) we postpone PEP 418 until there is some real-world experience with using > the os clocks from Python and we can develop a consensus of what is actually > needed rather than what people think we need (i.e. probably in 3.4); > > 4) if the standard library has need for a "use the best clock available, for > some definition of best, and fall back to time() if not" clock, then the time > module should do the simplest thing that could possible work, flagged as a > private function: +1 on overall idea too. - Yury _______________________________________________ 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
