Repository navigation
BUG: read_json(orient="table") raising for tz-naive datetime fields with offsets (GH#52595) - #71322
Open
jbrockmendel wants to merge 1 commit into
Open
jbrockmendel wants to merge 1 commit into
jbrockmendel wants to merge 1 commit into
Conversation
jbrockmendel
marked this pull request as ready for review
October 19, 2026 21:50
…ith offsets (GH#52595) pandas<1.5 wrote tz-naive datetimes with a "Z" suffix, so table-orient JSON from those versions failed to read since 2.0. Parse such fields as UTC and drop the tz, matching 1.5.3. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jbrockmendel
force-pushed
the
bug-52595
branch
from
November 7, 2026 20:02
c0456d5 to
761bacd
Compare
This branch has not been deployed
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.
closes #52595
pandas<1.5 wrote tz-naive datetimes with a
Zsuffix (fixed in GH-38760), soorient="table"JSON from those versions has a{"type": "datetime"}field with no"tz"whose values carry an offset. Since 2.0 theastype("datetime64[ns]")inparse_table_schemarefuses these andread_jsonraises. Such fields are now cast to UTC and the tz dropped, giving the tz-naive UTC wall time as 1.5.3 did. Values without an offset are unaffected, and parsing still goes through the sameastype, so non-ISO strings and error messages are unchanged.AI disclosure: drafted with Claude Code (
claude opus 5.5 (high)), used to diagnose the regression, write the fix and test, and review the branch.