-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build fails on Mac OS X 10.8.5 (12F45), xcode 5.1.1 (clang) #1013
Comments
Without being able to replicate this I suspect that this relates to the |
This definitely helps (pip reports success). However, I can't import from
And same for just import cryptopgraphy My site-packages has a new directory, with contents:
_Cryptography_cffi_8f86901cxc1767c5a.so* --Jeremy On Sun, May 4, 2014 at 10:11 AM, Paul Kehrer [email protected]:
|
So it built the modules but didn't install the actual python code... What version of pip are you running? Could you upgrade to the latest and try again? |
success! thanks much. I did hit a small bump along the way, but its a pip 1.5.5 thing rather than cryptography thing. In case its useful to someone, here are the details: I had pip 1.2.1, so I just upgraded to pip 1.5.5, uninstalled cryptography, and tried again. The resulting error from pip was surprising, and happens for all the packages I've tried (not just cryptography). I can clearly see stuff if I point a browser at https://pypi.python.org/simple/cryptography/ . And I get same error if I try with sudo:
So I manually downloaded the tarball for v0.3 and did:
pip reports success and I can import cryptography from within python. |
I bet if you do |
yes indeed. certificate verify failed, seemingly due to the more recent version of pip using an old / bad version of openssl (?!)
from looking at your comments from a year ago here pypa/pip#829 I get
my default (Mac) version of openssl is more recent (OpenSSL 0.9.8y 5 Feb 2013) |
Where did you get your current Python from? I assume it came from some distribution? |
EPD canopy: Enthought Python Distribution -- www.enthought.com I've been using 32-bit python due to some libs needed for a package that I contribute to. Hopefully possible to go to 64-bit python soon. |
thanks everyone--very helpful. @Ivoz I'm not sure what you are suggesting -- do a fresh re-install of everything canopy-related? The most recent version of pip I am seeing through the canopy package manager is v1.0.2 |
That, or find out if enthought has a way of upgrading OpenSSL for their previous releases. pip 1.0 is now 5 minor releases behind :( |
Thanks much, very sensible. If anyone with the same issue ever reads this far, this old SO posting looks relevant http://stackoverflow.com/questions/15441224/can-i-relink-enthought-python-to-new-version-of-openssl-on-mac-os-x |
I've tried installing two ways: via pip, and by cloning from github followed by setup.py. Both give me:
I've looked at issue #813 and #823, which seem unrelated. The closest thing I've found online is this thread (unrelated to the
cryptography
project): http://sourceforge.net/p/fink/mailman/fink-users/thread/[email protected]/Following that thread, I checked and it looks like I have a file of the right name 'CommonKeyDerivation.h' in a reasonable place:
At this point I'm at a loss, advice much appreciated.
Here's my gcc version (= clang):
Not sure if this is relevant or not:
And finally, the full output when trying to install:
The text was updated successfully, but these errors were encountered: