FWIW I think that ``python -m venv`` is the easiest (only?) way to reliably say that you want to create a virtual environment for *this* particular Python. This is especially important when multiple versions of Python that have venv start to be able to be installed (either via the system repos, or via PPAs like deadsnakes). In particular, there is an inprogress rewrite of virtualenv to use the venv module for isolation that will essentially be doing ``python -m venv``.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290847 Title: pyvenv fails due to mising ensurepip module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
