Package: python3-venv
Version: 3.4.2-2
Severity: important
Dear Maintainer,
I'm trying to mimic the behavior of --system-site-packages in python2's
virtualenv package in python3's venv package. The following should demonstrate
the problem:
$ python2 -m virtualenv --system-site-packages venv2
$ source venv2/bin/activate
$ which pip
/tmp/asdf/venv2/bin/pip
$ deactivate
$ python3 -m venv --system-site-packages venv3
$ source venv3/bin/activate
$ which pip3
/usr/bin/pip3
$ deactivate
As you can see, in the python3 case, I am using the system pip3. As a result,
if I try to run `pip install [package]` it will try to install it outside the
virtual environment. This does not happen when not using the
`--system-site-packages` flag.
-- System Information:
Debian Release: 8.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python3-venv depends on:
ii python3 3.4.2-2
ii python3.4-venv 3.4.2-1
python3-venv recommends no packages.
python3-venv suggests no packages.
-- no debconf information
