Retire psyplot recipe and diagnostic

[valeriupredoi]

Description

• Closes Retire recipe_psyplot.yml together with its diagnostic psyplot_diag.py #4062
• Link to documentation: https://esmvaltool--4063.org.readthedocs.build/en/4063/
• this PR and Remove Julia from conda dependency environment (but keep tests for esmvaltool install Julia) and add docs how to install from source #3921 will immediately release full functionality for Support Python 3.13 #3805

---

Before you get started

• ☝ Create an issue to discuss what you are going to do

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

• 🛠 This pull request has a descriptive title
• 🛠 Documentation is available
• 🛠 Tests run successfully
• 🛠 Any changed dependencies have been added or removed correctly
• 🛠 All checks below this pull request were successful

[bettina-gier]

The psyplot diagnostic also has an api page that should still be removed from the doc. I'd also not add a legacy recipe to the broken recipe list.

[valeriupredoi]

cheers @bettina-gier - API removals in 504737d 6b51eda and 0714fe4

[bettina-gier]

looks good now, and nice catching the FAQ paragraph

[valeriupredoi]

looks good now, and nice catching the FAQ paragraph

many thanks @bettina-gier 🍺 Since this all was done by @schlunma (sorry buds!) could I get a nod from him as well, please, and from @katjaweigel since she mentioned she kinds needs the psy diag 🍺

[schlunma]

Thanks V!

2 points:

• You need to remove the reference to the API doc here:

  ESMValTool/doc/sphinx/source/recipes/recipe_psyplot.rst

  Line 23 in 89fc58b

  * :ref:`psyplot_diag.py <api.esmvaltool.diag_scripts.psyplot_diag>`

  . No idea why the doc builds with this.
• There is also a mention in ESMValCore about this which needs to be removed: https://github.com/ESMValGroup/ESMValCore/blob/82d795ecbd295de740f27e134d64e24e278cd562/doc/quickstart/find_data.rst?plain=1#L515

[valeriupredoi]

thanks, Manu 🍺 API ref removed in 3af5325 - I'll open a PR in Core to remove that, on Monday, pub time now 🍻

@schlunma EDIT: Tuesday, since I had forgotten we have Monday off, but here is the Core PR (thanks for pointing me to that ref!) ESMValGroup/ESMValCore#2741

[katjaweigel]

Thanks @valeriupredoi !
My first thought was, that it would be better to have a replacement first, but Tina reminded me, that it is not working any more already now with up to date python, so it is probably better to remove it.

[valeriupredoi]

Thanks @valeriupredoi ! My first thought was, that it would be better to have a replacement first, but Tina reminded me, that it is not working any more already now with up to date python, so it is probably better to remove it.

hi @katjaweigel sorry we had a bank holiday in the UK yesterday; indeed, the psy packages always need to be updated manually, and that was fine before Python 3.13, and, in fact, also to answer @bouweandela , I am a maintainer of some of them on conda-feedstock, so I tried to help as much as possible; unfortunately, the situation now is that the packages suffer not from a technical problem, but rather, from a functional (scientific) issue, that Phillipp had struggled to fix, and I have no clue what the actual problem is, since he does his testing on an Azure platform that I don't have access to, so things are a bit trickier than a simple issue with maintenance.

I will merge this one now, and make the Python 3.13 PR ready, but will also try and see if we can replace this recipe with one that uses more easily to maintain dependencies, I promise. Cheers, and very sorry for the inconvenience 🍺

[valeriupredoi]

sad to see this going but happy to have us back on the modern env path 🍺