You have to install python3-venv, this will make the ensurepip module available, and the creation of a virtualenv will succeed
Imho this is an horrible naming choice: the error you'll get when trying to run `python3 -m venv` mentions ensurepip, and most ubuntu/debian users might have heard about the fact that ensurepip is disabled in the distro
then, `apt list ensurepip` or `apt search ensurepip` won't yield any useful results (just like I tried to do, before being puzzled about the "fix released" status of this bug)
moreover, `--without-pip` will just work even without the new package, making the name "python3-venv" even more misleading
Still, I'd caution you AGAINST using venv... I just found another trivial bug. You're better off using virtualenv, given how it's battle tested
@rspeer @wolfgang-richter
The bug is "sort of fixed"
You have to install python3-venv, this will make the ensurepip module available, and the creation of a virtualenv will succeed
Imho this is an horrible naming choice: the error you'll get when trying to run `python3 -m venv` mentions ensurepip, and most ubuntu/debian users might have heard about the fact that ensurepip is disabled in the distro
then, `apt list ensurepip` or `apt search ensurepip` won't yield any useful results (just like I tried to do, before being puzzled about the "fix released" status of this bug)
moreover, `--without-pip` will just work even without the new package, making the name "python3-venv" even more misleading
Still, I'd caution you AGAINST using venv... I just found another trivial bug. You're better off using virtualenv, given how it's battle tested