Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment:
On Mon, Jul 12, 2010 at 1:06 PM, Antoine Pitrou <rep...@bugs.python.org> wrote: .. > Indeed, the GIL code would probably still use its own code paths. > However, other less sensitive code could rely on the new API. For > example, it is not critical for lock timeouts to benefit from the full > gettimeofday() precision. That may be true, but I would rather proceed in small steps. First expose it in _time.h so that it is shared by time and datetime modulesand then if specific uses are found inside core python, move it to a more appropriate header. Lock timeouts are not a good use case for gettimeofday because POSIX APIs use nonoseconds instead of microseconds. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9079> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
