On 9/21/2026 5:17 PM, Martin Schöön wrote:
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

Dear Martin,

Sadly, I am completely unfamiliar with Conda, nor do I know anything
about managing Python environments yet.  So I only have a suggestion
for the intermesso [0], and hopefully the wizards of comp.lang.python
have a better answer.

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.


Best wishes, and happy Python!

[0] I simply presume someone is listening to music while we wait for the
wizards to reply.

[1] Somewhere, someone is coding a Linux package manager from scratch,
hence if there are /n/ today, there will be /n+1/ tomorrow.
--
Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
I'm not from the Internet, I just work there. | via XS News
https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
--
https://mail.python.org/mailman3//lists/python-list.python.org

Reply via email to