May 12, 2016
2:14 a.m.
On 5/11/2016 7:48 PM, Chris Angelico wrote:
* C on POSIX: integer seconds (usleep and nanosleep for integer micro/nanoseconds) * C on Windows: integer milliseconds
Ditto for tcl/tk 'sleep' function: widget.after(ms, func, *args)
* Pike and Python: int or float seconds * REXX on OS/2: integer seconds [syssleep], milliseconds [rxsleep], or decimal seconds
So if you're doing cross-language work, you'll need to check your docs anyway,
Moving from sleep(seconds) to .after(ms) is a nuisance that sometimes trips up SO questioners, but it is near the bottom of the list of newbie problems with tkinter. -- Terry Jan Reedy