-
-
Notifications
You must be signed in to change notification settings - Fork 11.3k
Homebrew doesn't upgrade pip / distribute on Python upgrade #20074
Comments
Duplicate of #19047? |
Maybe, but I fixed it locally pretty easily - just changed the link in pip script from 2.7.3 to 2.7.5. |
I was having a similar issue before I posted #19047. The old pip script was not removed from /usr/local/share/python on upgrade, so I removed it manually. Now, it seems to install to /usr/local/bin instead, so maybe you have the old path first in your PATH first. |
Sorry for the inconvenience. Will be fixed by #18588 which I hope to ready soon. As you can see there, a few formulae have to be checked and adapted by me before I can push that. In short: pip will be put into the |
I am having the same problem on the latest version of |
@oryband and @jbeezley Okay, I pushed 0b50110, which fixes the issues of upgrading pip/distribute (hopefully) because pip is installed into @subszero MacVim should work now also. At least on my Mac. If you still have trouble, please open a separate issue. I can call I suggest to |
@samueljohn pip/distribute was indeed linked correctly, but I'm still getting I had to Please re-open. |
@samueljohn I tried this and it doesn't seem to be working after the 2.7.5 update for python. Before that, I had followed the same procedure to solve the problem. |
@subszero check the links in my post above you, Macvim still links to system Python. This is a Macvim bug that should be fixed I suppose. I think @samueljohn is on it. In the meanwhile you should |
For the record: MacVim works now with a brewed python to, but we had to be pretty harsh in persuading it to do so. In the |
If you upgrade to Python 2.7.5 from 2.7.3 for example, the pip script still points to 2.7.3 instead of pointing to 2.7.5. This should be done automatically.
The text was updated successfully, but these errors were encountered: