Repository navigation
gh-160368: Detect sem_clockwait at runtime on Linux - #160371
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When Python is built with older Linux libc headers, timed semaphore waits use the real-time clock even if
sem_clockwaitis available at runtime. Use a weak reference on supported compilers to selectsem_clockwaitat runtime, falling back tosem_timedwaitwhen the symbol is absent. ThreadSanitizer builds continue to use the real-time clock.Addresses astral-sh/python-build-standalone#1176.
Closes #160368.
sem_clockwaitavailability at runtime on Linux #160368