Just wanted to document this here instead of in a commit comment...PyCrypto 2.4 does not install cleanly on any system I've tried, which is why all latest Fabric/ssh versions require Crypto <2.4.
Same thing happens if one obtains the source code for e.g. fabric or ssh or paramiko, and runs their
I can replicate this error in clean virtualenvs under:
and in a global, non-virtualenv (but otherwise mostly clean) environment under:
So, it's also not just a virtualenv related issue.
I have encountered the problem when logged in as as user which is not myself, so it seems unlikely to be something in my specific environment setup.
I'll submit this to Crypto upstream sometime soon, but for now my software does not need any of the new features in 2.4 and it's not worth the effort to figure out if we can somehow fix it on our end (which seems unlikely.)
The text was updated successfully, but these errors were encountered:
Interestingly, when I ran
I am creating a completely vanilla 11.04 VM to see if this was something we added, or if Ubuntu is now using Distribute full-time. EDIT: Yea,
On my OS X 10.7 box,
I think I've done enough research here to assert that it does not install well on two major platforms, virtualenv or no virtualenv, and only via easy_install/setup.py. I've gotten reports from a few folks that did not have problems building Crypto from its setup.py (one of which was on Windows) so it's still unclear exactly where the problem lies, but it's definitely not something niche.
Crypto just pushed 2.4.1 which fixes this problem; I have updated all Fabric related setup.py files (Fab 1.1, 1.2 and
Will push a release this weekend probably.