Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What's new updates for v3.11.1 . #6271

Merged
merged 1 commit into from
Dec 19, 2024
Merged

What's new updates for v3.11.1 . #6271

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions docs/src/whatsnew/3.11.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,20 @@ This document explains the changes made to Iris for this release
And finally, get in touch with us on :issue:`GitHub<new/choose>` if you have
any issues or feature requests for improving Iris. Enjoy!

v3.11.1 (19 Dec 2024)
===========================

.. dropdown:: |iris_version| Patches
:color: primary
:icon: alert
:animate: fade-in

The patches in this release of Iris include:

#. We added in a :class:`~iris.Future` flag - ``date_microseconds``, which
prevents floating point problems arisen from :class:`cf_units.Unit` v3.3.

#. We pinned dask to <2024.9 to prevent an indexing bug.

📢 Announcements
================
Expand Down Expand Up @@ -73,6 +87,14 @@ This document explains the changes made to Iris for this release
#. `@ESadek-MO`_ updated to the latest CF Standard Names Table v86
(5 September 2024). (:pull:`6200`)

#. `@trexfeathers`_ added a new :class:`~iris.Future` flag -
``date_microseconds`` - which sets whether Iris should use the new
microsecond-precision units (see :class:`cf_units.Unit`, microseconds
introduced in version 3.3) when the unit
is a time unit. The previous maximum precision was seconds. You should check
your code for new floating point problems if activating this (e.g. when
using the :class:`~iris.Constraint` API). (:pull:`6260`)

🐛 Bugs Fixed
=============

Expand Down Expand Up @@ -116,6 +138,10 @@ This document explains the changes made to Iris for this release
the concatenation axis. This issue can be avoided by disabling the
problematic check. (:pull:`5926` and :pull:`6187`)

#. Note that due to the new ``date_microseconds`` :class:`~iris.Future` flag,
the time coordinate categorisation speedup introduced above
will only be available when ``iris.FUTURE.date_microseconds == True``.

🔥 Deprecations
===============

Expand All @@ -135,6 +161,9 @@ This document explains the changes made to Iris for this release

* `NumPy v2 changed scalar printing`_

#. `@stephenworsley`_ pinned dask to <2024.9 due to an indexing bug. (:issue:`6251`,
:pull:`6255`)


📚 Documentation
================
Expand Down
Loading