Ubuntu
python-pip package

  1. Bug #1512792
  2. Comment #15

Comment 15 for bug 1512792

Revision history for this message
Otus (jan-varho) wrote :

I was getting a similar error on 16.04 by running "python -m pip", but *not* when running "pip" directly. Upgrading CFFI per comment #3 fixed it.

This is with a system upgraded from Trusty (and before) in case that matters.