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 Gammaguy, eryksun, josh.r, paul.moore, rhettinger, steve.dower, tim.golden, vstinner, xtreak, zach.ware
Date 2018-08-29.23:19:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1535584755.85.0.56676864532.issue34535@psf.upfronthosting.co.za>
In-reply-to
Content
I dislike the idea of documentation the Windows clocks in the queue documentation, it's not the right place. I dislike the idea of documentating Windows "internals" in the Python documentation. You should see Python as a "thin wrapper" to the operating system. If you have an issue on a platform, you should look at the platform documentation. Python already provides time.get_clock_info('monotonic').

From what I read, changing the system clock resolution is a bad idea, since the Windows kernel is not designed for that, and it can reduce the battery life.

About Windows vs Linux, as I wrote, you are looking at the wrong way. queue.get() is not a bottleneck if you use threads, asyncio, multiprocessing or whatever.

Again, this issue is not a bug. And I dislike the idea of documentating the behaviour. So I still consider that the issue should be closed as "not a bug". But I leave it open since it seems like you want to use it to discuss Windows clocks ;-)
History
Date User Action Args
2018-08-29 23:19:15vstinnersetrecipients: + vstinner, rhettinger, paul.moore, tim.golden, zach.ware, eryksun, steve.dower, josh.r, xtreak, Gammaguy
2018-08-29 23:19:15vstinnersetmessageid: <1535584755.85.0.56676864532.issue34535@psf.upfronthosting.co.za>
2018-08-29 23:19:15vstinnerlinkissue34535 messages
2018-08-29 23:19:15vstinnercreate