STINNER Victor <vstin...@redhat.com> added the comment:
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 ;-)
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue34535>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
