4 ms·
Why not use pyenv + pyenv-virtualenv ? https://github.com/pyenv/pyenv https://github.com/pyenv/pyenv https://github.com/pyenv/pyenv-virtualenv https://github.
by shtsh 9y ago
Why not use pyenv + pyenv-virtualenv ?
https://github.com/pyenv/pyenv https://github.com/pyenv/pyenv
https://github.com/pyenv/pyenv-virtualenv https://github.com/pyenv/pyenv-virtualenv
- jjawssd 9y agopyenv with the virtualenv plugin provides the most sane default setup. what's missing is the buzz and the tutorials that utilize pyenv. pyenv is the best python interpreter management solution for me.
- geoelectric 9y agoI personally found that the way pyenv conflated python versions and environments when using this produced confusing behavior around pyenv local settings and other features. At the time I tried it, there was also some opinionated behavior going on regarding shell prompt modification, etc., that caused it not to inform my prompt theming correctly. Ultimately, I decided I didn't really want pyenv determining how I used virtualenv, I just wanted virtualenv to work well in pyenv. The opinionated dynamic may have changed since then, but for me the happy medium has been pyenv-virtualenvwrapper. Instead of pyenv trying to take responsibility for my virtualenv behavior, it just takes responsibility for implicitly enabling virtualenv+wrapper on any given python version on first use. That's the right split for me.