Sujet : Best practise for managing Conda environments?
De : martin.schoon (at) *nospam* gmail.com (Martin Schöön)
Groupes : comp.lang.pythonDate : 21. Sep 2026, 10:17:29
Autres entêtes
Organisation : @ Home
Message-ID : <nhcb19FjpohU1@mid.individual.net>
User-Agent : slrn/1.0.3 (Linux)
I am a occasional Python user and hence only post here rather seldom.
Full time lurker though :-)
I am a full time Linux user and moved from pip to conda for managing
my Python life a few years ago. I am not an advanced conda user by
any measure. For the most part moving to conda was a good idea.
Yesterday, however, I encountered a problem that a quick internet
search told me is somewhat common: adding a package to an environment
stalls at the 'solving environment' stage. I found a bunch of rather
different 'fixes'. I have not tried any yet. I think maybe I am doing
environments wrong.
Among the 'fixes' suggested are:
* Use mamba for installing packages.
* conda config --set channel_priority strict
* Remove and re-create environments to ensure packages are up-to-date.
The last one was not stated explicitly. I created it by
'interpreting' several posts that made me think I have done environments
the wrong way.
My thinking now:
I should have more rather than fewer environments and make them more
task specific -- avoid 'general purpose' environments to limit the
number of packages in each environment.
I have noticed that "conda update whatever" /always/ tells me everything
is up-to-date. This can't be true. Will the procedure of the third
bullet above solve this?
No, I have not tried asking any LLM. I hope for some real human advice.
TIA
/Martin
Haut de la page
Les messages affichés proviennent d'usenet.
NewsPortal