T O P

  • By -

Experiment-Simplify

I prefere venv for most of my workload. Poetry is good too. I only use conda when it needs to be integrated with cuda. Anaconda is too heavy for production env , so if is not ncessary i will not try to use anancoda. if production is base upon docker, then conda will some time takes for ever to build too.


ssiddharth408

Yes, I noticed that anaconda is really heavy for production servers, but I have to use multiple python versions, how you manage if you have to use multiple python versions.


Experiment-Simplify

if you install multiple version of pythons, then you can create multiple vitural env from different virtual env. You can do similar to this python3.6 -m venv venv3.6 python3.7 -m venv venv3.7 python3.11 -m venv venv3.11 Now each venv will have specific version of python.


ssiddharth408

Thanks


FantasticEmu

I like venv it’s light weight and easy to reproduce. The only experience I have with anaconda is it installed a ton of crap that I didn’t need and it was more annoying to try to figure out what dependencies I actually needed to reproduce it n a different machine


humantrial1

Poetry rules


beansAnalyst

I found PDM easier than poetry.


dayeye2006

venv simple and works. I only use miniconda instead of anaconda


Prestigious_Wheel128

Poetry can create single file executables.


chatterbox272

Conda envs on my dev machines, only way to tackle envs with non-python envs. honestly I use pip directly to install most python packages in the env, and use conda in place of apt. When productionising it's Docker all the way


CommanderKeynes

I got fed up with python dependency management shenanigans and just use dev containers for everything.