Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
All commit authors signed the Contributor License Agreement. |
Documentation build overview
|
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.
On current macOS,
CDLL("libfoo.dylib")no longer finds libraries in/usr/local/libor/Library/Frameworks. I checked with the python.org 3.14.10 installer and with a non-codesigned build. dyld's search trace (DYLD_PRINT_SEARCHING=1) shows the only default fallback it tries is/usr/lib. This matches the dyld man page: binaries built with recent SDKs have no default fallback path. So the cause today is the SDK, not only the hardened runtime discussed in the issue.This adds a short note to the
CDLLdocs: use the full path, or setDYLD_LIBRARY_PATH/DYLD_FRAMEWORK_PATHbefore starting Python. Setting them throughos.environat runtime has no effect. I didn't suggestfind_library(), since it's soft-deprecated in 3.15.I used Claude Code to investigate, reproduce and draft this, and verified the behaviour myself on macOS 26.6 (arm64).