Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Martin =?UTF-8?Q?Sch=C3=B6=C3=B6n?= Newsgroups: comp.lang.python Subject: Re: Best practise for managing Conda environments? Date: 21 Sep 2026 20:33:53 GMT Organization: @ Home Lines: 35 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit X-Trace: individual.net 0Dzt1Y7swvemEYqmQeiN6QCOuejXnamqlqYFfCsACHmis/FdDi Cancel-Lock: sha1:bj/sw+fD7+lWQDSollkIMiNV5/s= sha256:vFOhfLy63SHoGa4yzLnkYT3jEvecr6E7x77+eUSca3E= User-Agent: slrn/1.0.3 (Linux) Xref: csiph.com comp.lang.python:198042 Den 2026-09-21 skrev Johann 'Myrkraverk' Oskarsson : > On 9/21/2026 5:17 PM, Martin Schöön wrote: >> >> 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. >> >> 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. >> > Dear Martin, > Have you considered installing the offending package using your opera- > ting system package manager instead, if available as such? There are > n+1 [1] Linux package managers, so I leave off any suggestions for the > command line tool. > I think this is how most or even all Linux users start with Python. Then, after a while you want to use a Python package (or version) not catered for by your system package manager... /Martin