Can I just run python -m pip without really having a clue what happens? 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. 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. 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
0 kommentar(er)
