Bug report

Bug description:

In bharel/asynciolimiter#14 we encountered an issue where both of these methods are waking up earlier than told by the clock.
It happens with both (normal event loop need to confirm) and with uvloop. In our case we've built a rate limiter, which is having issues because call later is not calling later 🤦‍♂️.

Should we offer the guarantee at the specification level that the scheduling will occur after the specified time, much like time.sleep() where it says "at least secs"?

CPython versions tested on:

3.12, 3.13

Operating systems tested on:

Linux, Windows

Linked PRs

• gh-127859: Fixed documentation for call_later and call_at regarding early wakeup. #137859