Repository navigation
Fix the time coding docs for pandas 3.1 - #11796
Merged
Merged
Conversation
pandas 3.1 gives microsecond resolution for numeric input with any unit, so the int64 extremes with unit='s' overflow. Build the timestamps from np.datetime64 instead, which keeps its resolution. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
LJimmy007
pushed a commit
to LJimmy007/xarray
that referenced
this pull request
Oct 24, 2026
Include the upstream pandas 3.1 documentation fix from pydata#11796 while preserving the reviewed query contribution. Co-authored-by: Codex <noreply@openai.com>
6 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The docs build fails since pandas 3.1, which gives microsecond resolution for numeric input with any
unit(release notes).pd.Timestamp(int64_min, unit="s")in the time coding page now raisesOutOfBoundsDatetime.np.datetime64, which keeps its resolution (same output with pandas 2.3, 3.0 and 3.1)Checklist
whats-new.rstAI Disclosure
Tools: Claude Code
🤖 Generated with Claude Code