STINNER Victor added the comment:
Victor>> Since the granularity is back, why not using also the resolution of
the selector in asyncio? :-)
Guido> Please, no. This has to stop.
Ok, sorry. If we still have some sporadic failures on UNIX, I think I will
maybe use Charles-François's suggestion: use at least 1 ms for the resolution
in asyncio loop: max(time.get_clock_info('monotonic').resolution, 1e-3).
But it looks like the issue is now fixed again on Windows.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue20505>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
