Package: python-virtualenv
Version: 1.11-2
Severity: important

Dear package maintainer(s),

Any virtualenv created with the --system-site-packages does not work as
expected. Any attempt to install a package with pip yields a permission
error.

Here is an easy example to reproduce this bug:

1) generate the failing and working venvs:
virtualenv --system-site-packages venv_failing
virtualenv venv_working

2) "source venv_working/bin/activate;pip install enum34" works

3) "source venv_failing/bin/activate;pip install enum34" does not work

A workaround is to create a virtualenv without the --system-site-packages
flag, manually copy its bin/pip and bin/easy_install scripts to the failing
virtualenv and change the paths in the headers of each script.

The changelog of v1.11.1 suggests a similar problem has been fixed
upstream. I'd suggest to update to the most recent version (v1.11.2 as of
today), and see whether this bug is fixed.

Thanks,


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-virtualenv depends on:
ii  python                2.7.5-5
ii  python-pkg-resources  2.1-1
ii  python-setuptools     2.1-1

Versions of packages python-virtualenv recommends:
ii  python-pip  1.4.1-2

python-virtualenv suggests no packages.

-- no debconf information
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Reply via email to