-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
Use monotonic time for sched, trace and subprocess modules #58895
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The PEP-418 added a new time.monotonic() function. The sched, trace and subprocess modules should use it, if available, to avoid issues when the system time is changed. Attached patch uses the time.monotonic() function when available. See also the issue bpo-14222 (same issue for queue and threading) and the PEP-418. -- socket and ssl modules should also use a monotonic clock if available, but these modules are implemented in C. The C implementation of time.monotonic() requires the librt library and is written in the timemodule.c. It requires more work to reuse it in the socket and ssl modules. |
LGTM. |
New changeset 1345cf58738d by Victor Stinner in branch 'default': |
It was a broken change for the |
Oh! You commented the change 12 years later. Does your comment mean that something should be changed? That the documentation is incomplete? |
The documentation definitely should be changed. |
Please open a new issue, or reopen this issue. |
See #103417. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: