On 12 November 2017 at 18:38, Antoine Pitrou <solip...@pitrou.net> wrote: > On Sun, 12 Nov 2017 12:20:45 +0000 > Paul Moore <p.f.mo...@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.
Thanks for the clarification. I was surprised by the assertion, but didn't have a Debian system to check, so it's good to know it's false. Paul _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
