(I ask because I had a bunch of issues getting

virtualenv

to play nice with the python interpreters I have installed on my Mac, but just doing this made it happy:

diff --git a/build-support/virtualenv b/build-support/virtualenv
index 06016fc1b..02c6bd156 100755
--- a/build-support/virtualenv
+++ b/build-support/virtualenv
@@ -24,21 +24,4 @@ fi
 
 log "Using Python at ${PY}"
 
-HERE=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
-if ! [ -f "${HERE}/virtualenv.dist/BOOTSTRAPPED-${VIRTUALENV_VERSION}" ]; then
-  pushd "${HERE}" >/dev/null
-    VIRTUALENV_PACKAGE_FULL_URL="${VIRTUALENV_PACKAGE_LOCATION}/virtualenv-${VIRTUALENV_VERSION}.tar.gz"
-    log "Downloading ${VIRTUALENV_PACKAGE_FULL_URL}..."
-    curl -#L -O "${VIRTUALENV_PACKAGE_FULL_URL}" || \
-      die "Failed to download ${VIRTUALENV_PACKAGE_FULL_URL}."
-    rm -rf virtualenv-${VIRTUALENV_VERSION}
-    tar zxf virtualenv-${VIRTUALENV_VERSION}.tar.gz || \
-      die "Failed to extract ${VIRTUALENV_PACKAGE_FULL_URL}."
-    # TODO(ksweeney): Checksum
-    touch virtualenv-${VIRTUALENV_VERSION}/BOOTSTRAPPED-${VIRTUALENV_VERSION} && \
-      rm -rf virtualenv.dist && \
-      mv -f virtualenv-${VIRTUALENV_VERSION} virtualenv.dist
-  popd >/dev/null
-fi
-
-exec "${PY}" "${HERE}/virtualenv.dist/virtualenv.py" "$@"
+"${PY}" -m venv "$@"

Ubuntu requires python-dev or python-venv, etc.

For example: https://packages.debian.org/buster/python3-venv

It depends on the distro - but a dev should be able to take the instructions - install a full python environment and deal with that imo.

You know your OS - or if you don't .... we can't teach you that really.

I think the short-take on this state of affairs in Linux distros is they treat CPython like the jvm and assume there is a JVM different from a JDK. There isn't afaict since the python docs don't say

ensurepip

or

venv

are somehow optional modules.