Shankar Unni added the comment: > If you want to modify time.sleep(), you must be careful of the portability: > Windows, Linux, but also Mac OS X, FreeBSD, Solaris, etc.
Oh, I totally agree. What I'm trying to do is to define another autoconf flag (HAVE_CLOCK_NANOSLEEP), that does a feature test and enable that flag, and just use that if available. Now that's a good point that if we have clock_nanosleep() on another platform (non-Linux) and it does the wrong thing, then I might have to add further discrimination. For now, one sticking point that I've stumbled across is that clock_nanosleep() requires "-lrt". Complicates the autoconf check a bit. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21302> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
