native-api

There's `*conda*-latest` if you want a rolling-release model and `*conda*-` that's supposed to be used to get specific conda releases. Each conda release ships with a specific release of Python,...

> I didn't find the way how to pass `local.yml` to `pyenv virtualenv` `pyenv virtualenv` can pass arbitrary long options to the underlying program -- but only long options (arguments...

**You need to add `~/.local/bin` to `PATH`.** In Ubuntu, this can be done by restarting the shell (its stock `~/.bashrc` only adds `~/.local/bin` to `PATH` if it exists at the...

Pyenv-Virtualenv creates environments with `virtualenv` if it is installed for the base Python. If it's not, it uses `-m venv` which indeed does not install `wheel`.

Note an important detail in both https://github.com/pyenv/pyenv-virtualenv/pull/430 and https://github.com/pyenv/pyenv/blob/e676fde9909946fc0078ec921936eb079c24fd8d/libexec/pyenv-init#L146-L147 : not only does it deduplicate PATH entries, it also pushes the entry to the start of PATH. Practice has shown...

> Ok. what does this mean in concrete terms for this PR? The PR should likewise push the PATH entry to the beginning of PATH.

You can't really commit a virtualenv to version control because it contains a reference to its base environment -- which is OS- and machine-dependent. You are supposed to instead commit...

SGTM

AFAICS, you can just copy the virtual environment's directory. And create a symlink to it in `$PYENV_ROOT/versions` if needed.

In any case, the cloning boils down to smth like: ```bash (pyenv shell $old; pip freeze >modules.lst) pyenv virtualenv $new (pyenv shell $new; pip install -f modules.lst) rm modules.lst ```...