At the moment running python -m venv venv or python3 -m venv venv creates a virtual environment that does not contain a python<major>.<minor> symlink, which results in executing whatever the default python is when running i.e. python<major>.<minor> within an activated virtual env. OTOH if one runs python<major>.<minor> -m venv venv, then everything is OK. Would it be possible to include a python<major>.<minor> symlink in all cases? If not, then I think we should update the docs to mention that somewhere, since it took me quite a while to figure this out.