native-api

Pyenv-Virtualenv make virtualenvs work like regular installations: they are global and persistent. If you rather need created-on-demand local, volatile virtualenvs bound to projects, that's a very different workflow and you...

I don't use Pyenv-Virtualenv and am not interested in maintaining it. Plus, with the amount of time I can donate now, I have my hands full with just the base...

> At some point along the line I just got used to the conda tool not being available from virtualenvs of my miniconda install and it wasn't that big a...

> `pyenv virtualenv 2.7.13 backend -f` should work. I just tried it and it continues to host previously installed packages. Indeed it does. However, those previously installed packages may not...

According to https://chadrick-kwag.net/adding-pip-config-file-in-virtualenv/ , you can simply put a `pip.conf` into the virtualenv directory. https://pip.pypa.io/en/stable/topics/configuration/#location confirms that.

WFM with Jython 2.7.3

Well, I'm the (main active) maintainer now. From what I can see in the codebase, Pyenv has never loaded, or it's documentation suggested to load by default, shell integration into...

The current README suggests putting the init line to `.zshrc`. So this is probably no longer relevant.

It doesn't seem possible to activate multiple virtualenvs at once -- because they are supposed to set envvars with the env's name (`VIRTUAL_ENV`, `CONDA_DEFAULT_ENV`).

If that's not a requirement though, we can try, with an experimental option or smth. Because software that interacts with virtualenvs may malfunction. At the very least, you won't be...