New Question: I don't really understand the steps I'm supposed to take here before running python -m pip, but I don't really see any difference whether or not I do these steps anyway. Python-config python2.7 python3 pythonw2.7Īnd running locate python after building the database like described gave me a super long list, which wouldn't fit here. Typing python and hitting tab (equivalent to compgen -c python) gave me python python2 python2.7-config pythonw That you so much!Įdit: I ran the advice given here and got the following results: which -a python python2 python2.7 python3 python3.6 While I love tech I've got no coding experience at all in this is just over my head. If anyone could help me out it would really be appreciated. Library/Python/3.8/lib/python/site-packages (21.1.1) mean it already fixed itself? And what happens if I ignore the problem? I followed the link but found no solution other than the Python workaround, which seems to be a short term solution.Īs far as I know have both pip version 19.2.3 as well as 21.1.1 and need to remove the old one right? But how do I do that? And does Requirement already satisfied: pip in. Since then I've been getting the same answer. To avoid this problem you can invoke Python with '-m pip' instead of running pip directly. Please see for advice on fixing the underlying issue. This will fail in a future version of pip.
So I ran topgrade again and it said WARNING: pip is being invoked by an old script wrapper.
#Remove python 2.7 mac big sur install
You should consider upgrading via the 'pip install -upgrade pip' command.īut I though well, seems like it updated itself. WARNING: You are using pip version 19.2.3, however version 21.1.1 is available. Looking for a solution on the web I found this article.įollowing the advice I ran xcode-select -install and restarted afterwards.Īfter running topgrade again I became a bit suspicious when it said.
#Remove python 2.7 mac big sur pro
Things worked for me (installed Python 3.6.0 on MacOS 11.4) without doing it.When using topgrade in homebrew (I installed topgrade after installing homebrew with brew install topgrade) on macOS big sur on a 2020 Intel 13" default upper specs MacBook Pro I ran into the following issue: xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun The answer by Jacob Anderson was right, but it’s worth noting that there's no need to perform the dangerous step: sudo rm -rf /Library/Developer/CommandLineTools Switch shell to new Python version: pyenv shell 3.6.15Ĭheck the currently used Python version: pyenv which python3
Install the required Python version with patch: arch -x86_64 pyenv install -patch 3.6.15 <<(curl -sSL \?full_index\=1) Then run the command below to install (changing 3.6.0 for the desired patch) CFLAGS="-I$(brew -prefix openssl)/include -I$(brew -prefix bzip2)/include -I$(brew -prefix readline)/include -I$(xcrun -show-sdk-path)/usr/include" LDFLAGS="-L$(brew -prefix openssl)/lib -L$(brew -prefix readline)/lib -L$(brew -prefix zlib)/lib -L$(brew -prefix bzip2)/lib" pyenv install -patch 3.6.0 > ~/.zshrcĪdd environment variables (in my case the problem was with zlib and openssl): export LDFLAGS="-L/usr/local/opt/zlib/lib"Įxport CPPFLAGS="-I/usr/local/opt/zlib/include"Įxport LDFLAGS="-L/usr/local/opt/ /lib"Įxport CPPFLAGS="-I/usr/local/opt/ /include" bashrc using: nano ~/.zshrc or nano ~/.bashrcĪnd add: export PATH="$HOME/.pyenv/bin:$PATH"Įxport LDFLAGS="-L/usr/local/opt/zlib/lib -L/usr/local/opt/bzip2/lib"Įxport CPPFLAGS="-I/usr/local/opt/zlib/include -I/usr/local/opt/bzip2/include"Īfter editing and saving that file, run. Whether you chose to skip the last step or not, continue by editing. The solution was to follow brew reinstall zlib bzip2įrom people's comments (thanks to Lukasz Czerwinski and Alex Veksler) it seems many view this next step as optional (and even dangerous) and prefer to skip it though, it's worth a try if nothing else is working: sudo rm -rf /Library/Developer/CommandLineTools