-
-
Notifications
You must be signed in to change notification settings - Fork 11.3k
Pip "unsupported hash type" errors after installing Python #22816
Comments
Oddly enough, after I restarted my Terminal window, pip is now working just fine. Perhaps the formula should be updated to reset whatever needs to be reset without requiring a new terminal session? Or it could give instructions to restart your Terminal session before using it? Or maybe my experience was just a fluke. |
Never mind. My window was just too small to see the errors. They were scrolling up off the window where I could not see them. So it turns out that, while pip seems to be working fine for me, it is still showing the |
I don't remember was this was the last time we saw it; something to do with openssl possibly. |
I ended up uninstalling Python 2 and 3 via homebrew, using the Python 2 that comes with OSX, installing pip via easy_install, and installing Python 3 from http://www.python.org/getit/ That solved the problem for me, but doesn't really explain what happened with my homebrew install. I'm willing to close the ticket as some sort of configuration fluke, but happy to help if there is any testing I can do on my system to make homebrew better. |
If I knew what to ask for to help diagnose this I would; thanks for the offer. We do have a similar case somewhere in the closed issues...but they're hard to search. Or at least emotionally hard to search. |
I'm having the same problem. I found another issue (#21329) that looks related. I followed the instructions on that issue. To wit: 1.brew (re)install openssl But I still get the same error. This output is from near the end of the output of
|
@hartsold I ended up deciding it was easier to install Python using the downloadable versions from here: http://www.python.org/getit/ – and while I'd like to have used homebrew to manage Python, I wasted a lot of time trying to figure out this issue. Once I went with the direct install (I used the version that came with my Mac for Python 2, and the downloaded installer for Python 3), everything was working again and I slowly regained sanity. |
I went the same route. Just figured I'd add to the post so folks would know this wasn't a one-off. |
Have a look at /usr/lib/libssl.dylib and /usr/lib/libcrypto.dylib. They should point to libssl.0.9.8.dylib and libcrypto.0.9.8.dylib respectively. Mine were pointing to some 1.0.0 version that I had linked myself manually like two years ago in order to get some pgsl lib to work at that time. |
Following fixed issue for me:
|
This solved the issue. Thanks mihgen |
Same issue on Mavericks and mihgen's solution worked. Thanks. |
@mihgen solution worked for me on 10.9.2 as well. If its worth noting, openssl had already been installed in my case, which gave this this warning on step 1: Warning: openssl-1.0.1f already installed And following commands 2-4 worked and resulted in functional pip. pip pip, hooray! |
thanks @mihgen |
The solution provided by @mihgen didn't work for me... I suppose that's probably because I used --build-from-source when installing python, but I need to do that. EDIT: it turns out I didn't and ignoring someone else's advice was the right thing to do here. |
@mihgen's trick didn't work on Mac OS X Yosemite 10.10 Beta 2. |
@fredrikbonander I'm having the same problem with 10.10 Beta 2 and haven't found a solution yet. Will update if I do! |
@AweStriker @fredrikbonander @victorquinn I ran into this Not sure what was causing same issue, but with different CLT setup, e.g. XCode 4.6.x, as originally reported. |
@mihgen saved the day man !! |
@dakcarto Thanks it worked! |
Is there not a cleaner solution than |
@DomT4 I think the above noted PR and upstream commit fixes the issue, at least where it was caused by the current CLTools not being recognized. If the problem still persists, then it is worth noting, for debugging purposes, that the symptoms are indicative of |
@mihgen |
brew doctor
jason@localhost:~$ brew doctor Your system is ready to brew.
brew --config
brew install -v python 2>&1
view the gist
Now, try to use pip
The text was updated successfully, but these errors were encountered: