Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upUvloop internal clock is not microsecond accurate #359
Comments
|
Easy repro: from asyncio.events import get_event_loop
import uvloop
loop = get_event_loop()
print('stdlib:', loop.time())
loop.close()
uvloop.install()
loop = get_event_loop()
print('uvloop:', loop.time())
loop.close() |
|
That's correct, libuv only has a millisecond accuracy for its timers. |
|
Oh dear, so it's not fixable I guess? |
|
Fixable by submitting a PR to libuv to allow higher resolution timers on platforms that support that. That's very doable (maybe you can work on a PR?) just might take a bit longer. |
|
FWIW, here's an old libuv PR that is related: libuv/libuv#1191 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PYTHONASYNCIODEBUGin env?: yesToday I debugged some failing tests in the httpcore project and it turns out they were relying on time passing between two subsequent operations. The code was running so fast, however, that the returned clock value on uvloop was the same as it was before, due to the lesser accuracy. This should hopefully be easy to fix.