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

> Strongly disagree. Conda, pipenv, pyenv, venv, poetry are all trying to solve the same problem (although conda tries to solve some other problems too).

Not really, some of these manage the issue of multiple system pythons (pyenv), while some manage isolated envs for particular projects (venv), and some try to be wholistic python project and dependency managers (pipenv, poetry, arguably venv + pip freeze, but that's not "wholistic"). Conda sort of tries to be all of the above as well as a bunch of other things (high performance options etc.)



Pyenv also has isolated envs for specific projects, poetry also tries to solve that problem.

There is a ton of overlap, denying that is disingenuous.


While there is overlap, there's also a ton of differences (pyproject for dependencies, dependency resolution, version locks).

I use both pyenv and poetry, and basically nothing else apart from the occasional call to pip.

I cannot imagine dropping poetry and only use pyenv, but I can imagine dropping pyenv (have been looking at asdf recently...)




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

Search: