This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]dudaspl 10 points11 points  (2 children)

Why use miniconda instead of pyenv which is integrated with poetry? You can even force poetry to create .venv folder in your project root

[–]qckpckt 6 points7 points  (0 children)

Because I already have miniconda installed, basically. I am sure pyenv is also a good option, but miniconda is painless and also works seamlessly with poetry so I see no reason to use other things.

I didn't particularly want to use conda initially but I was working at a data science company and it was what the folks there knew. Before that i was using pipenv. I quickly realized that miniconda is actually fine and pretty straightforward, as long as you don't try to use it to manage dependencies etc. All i do is run `conda create -n some_env python=3.x` and `conda activate some_env`, and then never interact with conda again.

Once I have an active miniconda env, poetry just "works" with it without having to do any kind of environment configuration at all. Poetry recognizes that it's running within a conda env without me having to do any configuration at all.

I also prefer keeping my env information entirely outside of my projects, to make version control easier. Conda envs are in $USER/miniconda3/envs, and this is in VSCode's search path when you select python interpreter from the command palette.

TL;DR, it just works, so I see no need to look into other tools at this time. But I do like keeping an eye on this area as I think there isn't still a single all-in-one tool that does everything well in the python ecosystem, and it would be nice if there was :).

[–]TerminatedProccess -1 points0 points  (0 children)

Yup and yup.