On Mon, 1 Nov 2004 01:50:29 -0500, Raymond Hettinger <python at rcn.com> wrote: > For the time being, I think it would be best to use sleep() instead of > utime(). While it costs three seconds, at least we know it to be a > platform independent test. It is rather late in the game to be > debugging OS specific problems introduced by a new check-in. Okay. I am convinced about using sleep() always. And two seconds will be enough to wait for new timestamp value. :) Will check it in right now. Hye-Shik
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4