Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I used pyenv in my previous company. At first it was fine, but after a while with multiple versions of Python installed, things stopped working. The right virtual env was not activated, etc. (It could have also been because our software updates like OS and security upgrades were pushed by desktop support). I removed all of it, and just resorted to installing multiple versions of Python the old way (downloading from python.org) and then use `python<version> -m venv /my/virtual/env` to manage my virtual environments. Things are more stable, and I don't feel like its magic. I am not going back to pyenv.


Works fine for me on macOS. I am using venv the same way you do except some global ones for certain tools.


I thought one of the advantages of pyenv was that you switched to also creating virtual envs using pyenv and managed virtual environments with it too. Maybe not.


Pyenv is for Python versions. There is a plugin for virtualenvs that can be useful for some specific cases but I rarely use it nowadays.


Also, when working on packages supporting multiple versions it was very helpful to use tox with pyenv.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: