-
Notifications
You must be signed in to change notification settings - Fork 44
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
Using link to execute relocated 3.11 bin/python3 fails to find libraries #31
Comments
I suspect that this is the relevant upstream change: python/cpython#29041 |
Possible workaround would be to replace the symlink with a shell script that basically does
|
I've been playing around with Without the exports, you get the
With the exports, the
This is very early testing, and understandably won't work particularly well if your Python deployments are more complicated than just installing the |
With @carlashley's tip, I was able to work around this by creating a simple shim script that can be invoked (the context here was addressing macadmins/python#48):
This script can put anywhere (such as
|
Actually, this works even without the two env variables. I used Munki's
Then:
It seems to correctly utilize the path of the directory it's in, rather than looking in |
We're using a symbolic link for munkireport-python3 to point to a relocated python framework:
Executing /Library/MunkiReport/Python.framework/Versions/3.11/bin/python3 works fine:
Calling it with the link fails to find platform dependent libraries:
A relocated 3.10 doesn't seem to have a problem with this:
I'm building with these options:
The text was updated successfully, but these errors were encountered: