setop/pyenv
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Removed mentioning of yet-to-be-added logic

Browse Source
This commit is contained in:
Ivan Pozdeev 2024-02-27 18:16:50 +03:00
parent 286ed531e5
commit 91f669c77f
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
plugins/python-build/README.md
View File

@ -120,11 +120,17 @@ The exceptions -- non-default options that are set by default -- are listed belo
##### Homebrew ##### Homebrew
Homebrew is used to find dependency packages if `brew` is found on `PATH`: In MacOS, Homebrew is used to find dependency packages if `brew` is found on `PATH`.
* In MacOS, or
* If the running Pyenv itself is installed with Homebrew
Set `PYTHON_BUILD_USE_HOMEBREW` or `PYTHON_BUILD_SKIP_HOMEBREW` to override this default. Set `PYTHON_BUILD_SKIP_HOMEBREW` to avoid using it.
---
Homebrew is NOT used in Linux by default because it's rolling-release which causes a problem.
Upgrading a Python dependency in Homebrew to a new major version (that `brew` does without warning)
would break all Pyenv-managed installations that depend on it.
You can use a community plugin [fix-version](https://github.com/pyenv/pyenv/wiki/Plugins#community-plugins)
to fix installations in such a case.
When Homebrew is used, its `include` and `lib` paths are added to compiler search path (the latter is also set as `rpath`), When Homebrew is used, its `include` and `lib` paths are added to compiler search path (the latter is also set as `rpath`),
and also Python dependencies that are typically keg-only are searched for in the Homebrew installation and added individually. and also Python dependencies that are typically keg-only are searched for in the Homebrew installation and added individually.