Message217233
> 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. |
|
Date |
User |
Action |
Args |
2014-04-27 00:26:44 | shankarunni | set | recipients:
+ shankarunni, vstinner, akira, yselivanov |
2014-04-27 00:26:44 | shankarunni | set | messageid: <1398558404.11.0.140799587927.issue21302@psf.upfronthosting.co.za> |
2014-04-27 00:26:44 | shankarunni | link | issue21302 messages |
2014-04-27 00:26:42 | shankarunni | create | |
|