[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

Change by Brandt Bucher : -- nosy: -brandtbucher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

Change by Brandt Bucher : -- pull_requests: -27755 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

Change by Brandt Bucher : -- nosy: +brandtbucher nosy_count: 3.0 -> 4.0 pull_requests: +27755 pull_request: https://github.com/python/cpython/pull/29505 ___ Python tracker ___

[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

Carlton Gibson added the comment: Hi Ned, Thank you for the reply. That explains a lot. I hadn't considered that SQLite would be statically linked. > I believe the original reason was to avoid linking with the Apple-supplied > system copy of the sqlite3 library. I can see that being a

[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

Ned Deily added the comment: Thanks for the report. However, I think you've drawn the wrong conclusion form what you've observed. The reason you are unable to do what you are trying to do is that the _sqlite3 module included with the python.org macOS Pythons is statically linked with its

[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

New submission from Carlton Gibson : Hi. On MacOS 11.3 "Big Sur", with the latest 3.9.4 installed with the official installer downloaded from python.org, the DYLD_LIBRARY_PATH environment variable is not being respected. This looks very similar to Issue40198