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
On 9/21/2026 5:17 PM, Martin Sch||||n wrote:<snip>
<snip>
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.
<snip>My thinking now:Dear Martin,
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.
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.
Den 2026-09-21 skrev Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid>:
On 9/21/2026 5:17 PM, Martin Sch||||n wrote:<snip>
<snip>
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.
<snip>My thinking now:Dear Martin,
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.
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...
On 2026-09-21, Martin Sch||||n <martin.schoon@gmail.com> wrote:
Den 2026-09-21 skrev Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid>:
On 9/21/2026 5:17 PM, Martin Sch||||n wrote:<snip>
<snip>
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.
<snip>My thinking now:Dear Martin,
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. >>>>
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...
Indeed. Using the operating system package manager for Python
packages is only feasible if you yourself are creating a package
for that operating system.
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
Python coders [1], and someone would know what to do about the original >problem.
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.
On 21 Sep 2026 09:17:29 GMT, Martin Sch||||n wrote:
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.
My impression of Conda is that itrCOs more suited to Windows/Mac
environments which lack native package management. For example, I
donrCOt see a package for Conda under Debian -- surely something as
useful as that is made out to be, would be supported. But itrCOs not.
The most complex piece of third-party Python-based code that I install
is Jupyter, and that goes quite nicely into a virtualenv maintained
with pip.
On 9/22/2026 6:05 AM, Jon Ribbens wrote:
On 2026-09-21, Martin Sch||||n <martin.schoon@gmail.com> wrote:
Den 2026-09-21 skrev Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid>:
On 9/21/2026 5:17 PM, Martin Sch||||n wrote:<snip>
<snip>
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.
<snip>My thinking now:Dear Martin,
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. >>>>>
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...
Indeed. Using the operating system package manager for Python
packages is only feasible if you yourself are creating a package
for that operating system.
Point taken. Now, what is worrying me, is the lack of answers about the Conda package manager. I was under the impression Usenet was full of
Python coders [1], and someone would know what to do about the original problem.
Is there really, in all of Usenet, nobody who knows how to solve this?
On 2026-09-22, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
On 9/22/2026 6:05 AM, Jon Ribbens wrote:
On 2026-09-21, Martin Sch||||n <martin.schoon@gmail.com> wrote:
Den 2026-09-21 skrev Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid>:
On 9/21/2026 5:17 PM, Martin Sch||||n wrote:<snip>
<snip>
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.
<snip>My thinking now:Dear Martin,
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. >>>>>>
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...
Indeed. Using the operating system package manager for Python
packages is only feasible if you yourself are creating a package
for that operating system.
Point taken. Now, what is worrying me, is the lack of answers about the
Conda package manager. I was under the impression Usenet was full of
Python coders [1], and someone would know what to do about the original
problem.
Is there really, in all of Usenet, nobody who knows how to solve this?
I've been using Python for nearly 30 years, but I'm afraid I've never
heard of this 'conda' thing of which you speak. I use 'pip' for nearly everything, but apparently 'uv' is the new hotness.
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.
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.
TLDR:
* Create task specific environments.
* Use mamba.
* Try, as far as possible, to instal all needed packages in one go.
* Don't mend/tinker with environments. Create new ones instead.
* Document your environments. README.md or something...
I also asked Duck.ai (front end for Mistral Small 4 in my case) for
advise. The results looks like a summary of the information I
linked to. I will post it separately after having read through
and figured out how to format it for usenet news.
/Martin
If you're wondering how to format text for Usenet, I like Emacs for this >task. I then paste into Thunderbird for posting, but that's because I'm
not inclined yet to figure out how to configure GNUS.
Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote or quoted:
If you're wondering how to format text for Usenet, I like Emacs for this
task. I then paste into Thunderbird for posting, but that's because I'm
not inclined yet to figure out how to configure GNUS.
To wrap paragraphs, I wrote a script in Python that uses dynamic
programming to find the globally best wrap and made it available
to vim via a key mapping. It was used to wrap this paragraph here.
I am not always satisfied with the results, and so I also format
many paragraphs manually and do manual hyphenation painstakingly
looking up German and English words in hyphenation dictionaries.
I also have written a Python module that also does hyphenation, and
which I plan to publish one day, but so far the code has not yet
been cleaned up. This hyphenation uses TeX's hyphenation patterns.
On 9/23/2026 4:17 PM, Stefan Ram wrote:
I also have written a Python module that also does hyphenation, andYou mean you coded up TeX's line breaking algorithm?
which I plan to publish one day, but so far the code has not yet
been cleaned up. This hyphenation uses TeX's hyphenation patterns.
Did you do it from
the book /TeX: The Program/, or /Digital Typesetting/?
I have alas not coded up TeX's hyphenation patterns, and only thought to
Now to get perfect line breaks in fixed width text the best method is to >construct the text carefully, and change the words with a thesaurus, and
the word order, and possibly write a completely new sentence. When I do >this, I usually do this with hyphenation also, and do not care about the >official rules, and just wing it. The only paragraph I did this in this >followup, is this one.
a database of hyphenated words.
Now, here are my two posts from 2024 with an early version of
my line breaker.
. So I have integrated my formulas with the line wrapping, but only
as a thin "proof of concept" that only handles the single operator
"^" and one-letter names/numbers in plain text.
Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote or quoted:
If you're wondering how to format text for Usenet, I like Emacs for this >>task. I then paste into Thunderbird for posting, but that's because I'm >>not inclined yet to figure out how to configure GNUS.
To wrap paragraphs, I wrote a script in Python that uses dynamic
programming to find the globally best wrap and made it available
to vim via a key mapping. It was used to wrap this paragraph here.
<snip>
My problem is the unique 'mark up' I need to weed out...
Also, some questionable tips are hiding among the good ones. I will keep
them but add comments. I think it illustrates nicely how careful you
need be when reading LLM produce.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 53:29:58 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,430 |