Update iris pin

[valeriupredoi]

Description

iris=3.5 is out and has a bunch of nice features and bugfixes; I think we should update our pin

---

Before you get started

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 and labels
• 🛠 Any changed dependencies have been added or removed correctly
• 🛠 All checks below this pull request were successful

---

To help with the number pull requests:

• 🙏 We kindly ask you to review two other open pull requests in this repository

[codecov]

Codecov Report

Merging #2026 (2e091d2) into main (be534fd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2026   +/-   ##
=======================================
  Coverage   92.78%   92.78%           
=======================================
  Files         236      236           
  Lines       12464    12464           
=======================================
  Hits        11565    11565           
  Misses        899      899           

[remi-kazeroni]

@valeriupredoi, what about waiting for iris 3.6.0 scheduled for Wednesday? And would such change of pin require a new release as for Python3.11?

[valeriupredoi]

hmm I was thinking we'd pin on 3.5 and obv can grab 3.6 once it's out - my idea was to grab the various bugfixes from 3.5. No need to release anything, just yet - this would be used only by the dev installations, and also for release testing (if we don't release a bugfix release after we'd merge this) 👍

[bouweandela]

@valeriupredoi I understand that this solves a few problems, but doesn't the tool run more or less fine with iris v3.4? Anyone doing a new installation will already get 3.5, so this would just stop people who want to upgrade an older environment from doing that.

And would such change of pin require a new release as for Python3.11?

Lower bounds on packages generally do not cause as much trouble as upper bounds. The Python 3.11 thing happens because we had an upper bound on a dependency in the last release. Because only recent versions of that dependency package support Python 3.11, this upper bound rules out all versions of that package on conda-forge that support Python 3.11.

[valeriupredoi]

@bouweandela they already have to upgrade quite a few bits in the env from the changes we made in the pins for supporting Python 3.11. I reckon we can slip this one through too. I am not ready to give up my dog for this so if you guys consider it unnecessary, am OK to close, but I do like my updated deps 😁

[valeriupredoi]

Because only recent versions of that dependency package support Python 3.11, this upper bound rules out all versions of that package on conda-forge that support Python 3.11.

Indeed. It's actually a combination of releasing the upper bound on esmpy (was <8.4) and placing a lower bound on prospector (now >=1.9, the only one that supports Py311)

[remi-kazeroni]

@valeriupredoi - is this still needed because the Dask distributed PR (#2049) put an lower pin to iris>3.6.0?

[valeriupredoi]

nope, well pointed out @remi-kazeroni 🍺 Ah, evolution 🐒