Le 12/11/2017 à 19:38, Antoine Pitrou a écrit :
On Sun, 12 Nov 2017 12:20:45 +0000 Paul Moore <p.f.moore@gmail.com> wrote:
Well, not exactly. Do you do python -m venv, or py -x.x -m venv or pythonx -m venv ? Wait, it's not installed by default on debian.
Seriously? Debian don't provide venv in the standard Python install? That's just broken.
Frankly, I don't know where the current discussion comes from, but on two recent Debian and Ubuntu setups, I get:
$ dpkg -S /usr/lib/python3.5/venv/__init__.py libpython3.5-stdlib:amd64: /usr/lib/python3.5/venv/__init__.py
Which, for the uninitiated, means "the venv module is provided by the Debian/Ubuntu package named libpython3.5-stdlib". That package is, in turn, a dependency of the "python3.5" package.
Screenshot from yesterday morning. On Ubuntu 16.04, LTS of most popular Linux distro based on debian: we can see venv is clearly missing. On the bright side, it does give you an error message. We should have that for pip as well ! Unfortunatly, the message gives you a wrong advice, as you had to run the: sudo apt-get install python3.6-venv command and not: sudo apt-get install python-venv And my students were stucks. And this was a traning with professional adults java devs. Imagine total beginers...
