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 germn
Recipients germn, pitrou, r.david.murray, vstinner, yselivanov
Date 2017-09-21.16:28:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506011296.52.0.652353751162.issue31539@psf.upfronthosting.co.za>
In-reply-to
Content
STINNER Victor, thanks for explanation!

I don't know if this issue has practical disadvantages, but such behavior seems to be confusing, especially, since it can be reproduced with event_loop.time() and asyncio doc says nothing about resolution -
https://docs.python.org/3/library/asyncio-eventloop.html#delayed-calls

Do you think this issue should be closed?
Should I make PR to add info about clock's resolution to asyncio documentation?
History
Date User Action Args
2017-09-21 16:28:16germnsetrecipients: + germn, pitrou, vstinner, r.david.murray, yselivanov
2017-09-21 16:28:16germnsetmessageid: <1506011296.52.0.652353751162.issue31539@psf.upfronthosting.co.za>
2017-09-21 16:28:16germnlinkissue31539 messages
2017-09-21 16:28:16germncreate