Updated notes about conda

[ChrisBarker-NOAA]

This is more or less, an update to: #1269, but adapted to the new structure.

However, conda is now talked about in two places:

Installing scientific packages

and

Project Summaries

perhaps one of them should simply be alink to the. other -- probably Project Summaries can ref to Installing scientific packages.

Though I'm not totally on board with that -- while conda was developed for, and widely used by the Scientific computing community -- it's a more universal tool than that so maybe?

---

📚 Documentation preview 📚: https://python-packaging-user-guide--1581.org.readthedocs.build/en/1581/

[ncoghlan]

I think the way you've done it here is a good compromise: enough detail inline for the scientific packages section to make sense, but the larger amount of info in the project description. If a reference were to be added, I'd make it from the scientific section to the project summary (but not at the expense of the inline explanation of the relevance of the tool).

The build failure picked up a genuine structural issue, though: the Anaconda link is duplicated because one of the new paragraphs should be moved up to replace the old intro paragraph outright (the fact the old intro paragraph references Anaconda 5.0 suggests the previous text is at least 7 years old)

Leaving my approval active (since I agree with the gist of the change), but putting some comments in line with a suggestion to fix the build error.

[ChrisBarker-NOAA]

@sinoroc, @ncoghlan: thanks for the copy-editing!

[ChrisBarker-NOAA]

fixed the netlib link ..

[webknjaz]

@ChrisBarker-NOAA looks like the anaconda website link breaks linkcheck. Could you take a look at addressing that?

[ChrisBarker-NOAA]

I'm confused -- this works for me right now:

https://anaconda.org/

?!?!

Maybe a blip at that time -- can it be re-run?

[webknjaz]

@ChrisBarker-NOAA I restarted it before tagging you and the error was the same, I believe. This likely means that their website rejects various automated non-browser requests. This might be based on HTTP headers, the user agent string or the fact that it originated from the GitHub Actions platform.
I'll trigger it again but I wouldn't hold your breath. We'll likely need to add it to linkcheck_ignore or find a better link.

[webknjaz]

yep... restarting did nothing: https://github.com/pypa/packaging.python.org/actions/runs/11584803433/job/32268247267?pr=1581#step:5:254

[ChrisBarker-NOAA]

OK -- added it to linkcheck_ignore and it's passing -- thanks!