Comment 1 for bug 889398

I ran into the same issue and the fix is already committed, actually. We pegged pycrypto at 2.3 as the most recent version that was compatible with both pip install and buildout.