This is still incredibly odd because your traceback still flows through /usr/local, which the apt installed pip would never do. So I think you have some stuff installed in /usr/local, and possibly a PYTHONPATH, that is breaking the system installed pip.
Note that on Debian (and derived) /usr/local/lib/python2.7/dist-packages is on the standard python2.7 sys.path *before* /usr/lib/python2.7/dist- packages expressly so that system administrators can modify how Python works, but it's also incumbent on the system admin to make sure that anything installed there won't break the system packages. It looks like this is what's happening for you. I doubt it has anything to do with the architecture of the machine. Please start by clearing out any custom stuff you might have in /usr/local/lib/python2.7/dist-packages and try again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555723 Title: pip is breaking in ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-cryptography/+bug/1555723/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
