Virtualenv breaks if python-configparser is installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-virtualenv (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The virtualenv package fails when the python-configparser is installed and I try and create a python3.3 virtualenv:
virtualenv --system-
Running virtualenv with interpreter /usr/bin/python3.3
Traceback (most recent call last):
File "/usr/lib/
import ConfigParser
ImportError: No module named 'ConfigParser'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/
import configparser as ConfigParser
File "/usr/share/
_KEYCRE = re.compile(
SyntaxError: invalid syntax
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/share/
from apport.report import Report
File "/usr/share/
import apport.fileutils
File "/usr/share/
from configparser import ConfigParser, NoOptionError, NoSectionError
File "/usr/share/
_KEYCRE = re.compile(
SyntaxError: invalid syntax
Original exception was:
Traceback (most recent call last):
File "/usr/lib/
import ConfigParser
ImportError: No module named 'ConfigParser'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/
import configparser as ConfigParser
File "/usr/share/
_KEYCRE = re.compile(
SyntaxError: invalid syntax
This is because virtualenv re-executes itself with the target python version, but runs the virtualenv.py file in /usr/lib/
Status changed to 'Confirmed' because the bug affects multiple users.