➜

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 terry.reedy
Recipients ZackerySpytz, taleinat, terry.reedy
Date 2019-07-24.07:15:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1563952542.65.0.253428434701.issue35771@roundup.psfhosted.org>
In-reply-to
Content 
I had forgotten about this, but by coincidence, it occurred again today, on 'x86 Windows7 3.7' after PR-14919 was merged.  This may be the same machine as I might have left '7' off 'Windows' in the original report.

The 'windows timer' is used for time.sleep.  From various web articles, I read that its resolution varies from 10 to 25, defaults to 15.8 milleseconds in Win7 (this is the figure I knew years ago), and defaults to 35 microseconds in Win 10.  (Not exactly agreement.) time.sleep is hardly accurate for small fractions of a second delays, and delays may be much longer.  I believe that root.after does better.

Zachery, what OS and version do you have?
History
Date User Action Args
2019-07-24 07:15:42terry.reedysetrecipients: + terry.reedy, taleinat, ZackerySpytz
2019-07-24 07:15:42terry.reedysetmessageid: <1563952542.65.0.253428434701.issue35771@roundup.psfhosted.org>
2019-07-24 07:15:42terry.reedylinkissue35771 messages
2019-07-24 07:15:42terry.reedycreate