This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients akira, shankarunni, vstinner, yselivanov
Date 2014-04-27.00:36:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZjSLz2dcFfyJxdU8_dJm+P8MTRN4gG3pkwmME=1Dxbyw@mail.gmail.com>
In-reply-to <1398558404.11.0.140799587927.issue21302@psf.upfronthosting.co.za>
Content
2014-04-27 2:26 GMT+02:00 Shankar Unni <report@bugs.python.org>:
>> 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.

I'm talking about the expected behaviour which can be found in the
documentation of the function:
https://docs.python.org/dev/library/time.html#time.sleep
History
Date User Action Args
2014-04-27 00:36:47vstinnersetrecipients: + vstinner, akira, yselivanov, shankarunni
2014-04-27 00:36:47vstinnerlinkissue21302 messages
2014-04-27 00:36:47vstinnercreate