touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #122070
[Bug 1513565] Re: libpython2.7 uses the 3.x name for ConfigParser
Why are you using toolchain-r? Are you sure that's where your getting
your libpython2.7-minimal from for trusty?
https://launchpad.net/~ubuntu-
toolchain-r/+archive/ubuntu/test?field.series_filter=trusty
This problem doesn't happen in a clean trusty chroot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1513565
Title:
libpython2.7 uses the 3.x name for ConfigParser
Status in python-pip package in Ubuntu:
Confirmed
Status in python2.7 package in Ubuntu:
Confirmed
Bug description:
Installing a minimal virtualenv on Trusty Tahr (using libpython-
minimal 2.7.10-4~14.04), I ran into crashes because:
File "/usr/lib/python2.7/ssl.py", line 491, in inner
import configparser
ImportError: No module named configparser
Looking at the code in ssl.py, it uses "import configparser" even
though the package is called "ConfigParser" in Python 2.7 (it changed
in 3.0), this means that a clean virtualenv cannot install any
packages using easy_install (since they're served over an https
connection which uses the code in ssl.py).
As a workaround, you can `pip install configparser` to install the
package under the 3.0 name or change the code to be `import
ConfigParser as configparser` to import the correct package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1513565/+subscriptions
References