[issue43964] ctypes CDLL search path issue on MacOS

Carlo Cabrera added the comment: Re option 3: relying on `DYLD_LIBRARY_PATH` or `DYLD_FRAMEWORK_PATH` isn't a great solution either because of SIP. It's can get impractical to use in many standard Makefile-based build systems, for example. (cf. https://github.com/qmk/qmk_cli/issues/60,

[issue43964] ctypes CDLL search path issue on MacOS

Victor Lazzarini added the comment: Hi Ned, thanks for your detailed response. I have to say that the LD_LIBRARY_PATH partially worked in some cases, the library got loaded. However in cases where there were dependencies, further issues appeared particularly when the link (as revealed by

[issue43964] ctypes CDLL search path issue on MacOS

Ned Deily added the comment: Thanks for the report! I've spent some time investigating it and the story behind it turns out to be a bit complicated, so bear with me. It's all tied in to Apple's attempts to improve the security of macOS. As of macOS 10.15 Catalina, Apple introduced new

[issue43964] ctypes CDLL search path issue on MacOS

Victor Lazzarini added the comment: I have looked at this closely and it appears Python 3.6.5 has a search path for libraries and frameworks that is missing in the newer versions (3.7 onwards). I can load libraries from /usr/local/lib and ~/lib without any difficulties in 3.6.5, just by

[issue43964] ctypes CDLL search path issue on MacOS

Change by Victor Lazzarini : -- versions: +Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue43964] ctypes CDLL search path issue on MacOS

New submission from Victor Lazzarini : With Python 3.9.4 ctypes.CDLL does not appear to find framework libraries installed in /Library/Frameworks. --- With Python 3.6.5: victor@MacBook-Pro ~ % python3 Python 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018,