Homebrew
How to use Homebrew while retaining previouslyy installed system Python modules #4456
Replies: 2 comments 1 reply
-
|
You can set https://docs.python.org/3/using/cmdline.html#envvar-PYTHONPATH to look in additional locations. |
Beta Was this translation helpful? Give feedback.
-
|
This is a pretty good suggestion, using I maintain several projects, some of which use Homebrew to install dependencies. These projects are installed by end users on a variety of platforms with Python installed in a variety of locations. I need to be able to detect an existing Python and add module paths appropriately. I think I may be able to dynamically retrieve the paths during installation with something like: /path/to/system/python3 -c 'import site; print(site.getsitepackages())' | tr -d '[],'then add those to Is this the preferred/recommended route to take to incorporate system Python modules in Homebrew's python? |
Beta Was this translation helpful? Give feedback.
-
|
Fixing up |
Beta Was this translation helpful? Give feedback.
-
Additional Info
Output of
brew configOutput of
brew doctorDescription of issue
Some Homebrew formula install Python3 as a dependency. My understanding is the Homebrew formula require Homebrew Python3 and cannot use the system Python3. However, previously installed python modules are no longer found as the Homebrew python3 appears first in the PATH after configuring the shell initialization with
brew shellenv.I've read some folks have altered the PATH so Homebrew locations come after system entries in order to pickup the system python3. Is this an acceptable solution? Is there a recommended approach to preserving existing Python modules when installing Homebrew?
I like Homebrew and really want to use it but if it cannot co-exist with an existing system Python3 then it may not be of practical use.
Beta Was this translation helpful? Give feedback.
All reactions