Bernát Gábor

Will be in the creator code here somewhere https://github.com/pypa/virtualenv/blob/main/src/virtualenv/create/via_global_ref/builtin/via_global_self_do.py that likely uses the information feeded by https://github.com/pypa/virtualenv/blob/main/src/virtualenv/discovery/py_info.py. Per the logs above CPython3Posix is the creator, so will be somewhere in...

@rkucsora do you see the same behaviour if you use the builtin creator instead of the venv one?

This project is only responsible of the builtin creator. The venv creator is managed by debian so for that you're looking at filling a bug for that projects tracker.

PR addressing this is welcome.

This used to be the case but we reverted this behaviour in #2224 to align with how the venv module does things.

What shell are you using?

I invite elvish maintainers to provide this first as part of a separate package (``virtualenv-elvish``) via https://virtualenv.pypa.io/en/latest/extend.html#activation-scripts, and once it's stable and used we can reopen this and consider merge....

We do provide a zipapp https://virtualenv.pypa.io/en/latest/installation.html#via-zipapp Which you can download versioned from ``https://github.com/pypa/get-virtualenv/blob/20.1.0/public/virtualenv.pyz?raw=true``

Perhaps, but only @ewdurbin could set that up 🤔

The files in get-virtualenv overwrite rather than append. So in public, we only have the latest version. Users can still access older versions by using the Github repo API. The...