touch-packages team mailing list archive

[Andy Caldwell <andy.m.caldwell@xxxxxxxxxxxxxx>]

See my first comment, this is specific to the toolchain-r version of
libpython-minimal (the issue was introduced in
https://launchpadlibrarian.net/221233027/python2.7_2.7.10-3~14.04_2.7.10-4~14.04.diff.gz).
A clean trusty is not affected.

Is there a way to raise bugs against a PPA?  If so I couldn't work out
how...

I was using toolchain-r for their g++-4.9 build (and my love for living
on the bleeding edge :D).

-- 
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