Skip to content

[pull] main from pydata:main#1008

Merged
pull[bot] merged 1 commit into
Illviljan:mainfrom
pydata:main
Jun 3, 2026
Merged

[pull] main from pydata:main#1008
pull[bot] merged 1 commit into
Illviljan:mainfrom
pydata:main

Conversation

@pull

@pull pull Bot commented Jun 3, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

* Use explicit ns unit for np.datetime64 in test parametrize

numpy >= 2.5 deprecates the 'generic' (unitless) datetime64/timedelta64
dtype. Constructing np.datetime64("2000") or np.datetime64("NaT") in the
parametrize list ran during pytest collection, and with
filterwarnings=error the resulting DeprecationWarning aborted collection
of the whole module on the upstream-dev CI. That in turn produced a
malformed pytest report and silently disabled the
issue-from-pytest-log-action auto-issue filer.

Pin the unit explicitly so collection stays clean on numpy nightly.

* Handle int64 NaT sentinel before timedelta64 multiplication

numpy >= 2.5 (numpy/numpy#31378, merged 2026-05-11) turns
int64.min * timedelta64 from a silent NaT into a hard OverflowError.
The CF time decode path relied on the silent NaT and now raises through
_check_date_for_units_since_refdate and _check_timedelta_range, surfacing
as `ValueError: unable to decode time units '...'` from decode_cf.

Detect the sentinel (and float NaN) up front so the multiplication path
only sees real numeric inputs. Regression coverage already exists via
the existing int64.min parametrizations of test_cf_timedelta and
test_roundtrip_timedelta64_nanosecond_precision.

---------

Co-authored-by: Illviljan <14371165+Illviljan@users.noreply.github.com>
Co-authored-by: Justus Magin <keewis@users.noreply.github.com>
@pull pull Bot locked and limited conversation to collaborators Jun 3, 2026
@pull pull Bot added the ⤵️ pull label Jun 3, 2026
@pull pull Bot merged commit c3a398e into Illviljan:main Jun 3, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant