Having additional scripts in your path can confuse software installed via Software packages are installed, and what additional flags to use when `./configure` scripts often look for *-config scripts to determine if Warning: "config" scripts exist outside your system or Homebrew directories. Working fine: please don't worry or file an issue just ignore this. Please note that these warnings are just used to help the Homebrew maintainers If you run brew doctor, it might have some complaints. pyenv install 3.7.2įinally, configure pyenv to use one of these Python versions by default. For a list of available versions, execute pyenv install -list. Now you try to install any python version you like by executing pyenv install $VERSION. > After installing macOS updates you will need to (re)install these headers!Īlthough not required, the pyenv wiki recommends installing some additional libraries.īrew install openssl readline sqlite3 xz zlib > sudo installer -pkg /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg -target / > Some development headers are required for compiling Python on your Mac. You first need to make sure you have installed the dependencies for building Python. However, if you now try to install a Python version, it will most likely fail. (Do not forget to reload your shell after changing its config.) brew install pyenv Simply installing pyenv using Homebrew and making a small change to the configuration of your shell is sufficient to get pyenv itself working properly. This post shows how to configure your system to avoid these problems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |