Skip to content

API: update read_json to follow general default of microseconds #63473

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

Jump to bottom
Open
jorisvandenbossche wants to merge 1 commit into
base: main
Choose a base branch
from
Open

API: update read_json to follow general default of microseconds #63473

jorisvandenbossche wants to merge 1 commit into from
+99 −41

Conversation

@jorisvandenbossche
Copy link
Member

@jorisvandenbossche jorisvandenbossche commented Dec 23, 2025

This updates read_json to:

  • follow the general default of microseconds (or nanos if needed for the precision of the string) when parsing string columns
  • follow the actual (inferred) date unit of the numeric input (by default to_json writes milliseconds), similarly as is now done in to_datetime

@jorisvandenbossche jorisvandenbossche added IO JSON read_json, to_json, json_normalize Non-Nano datetime64/timedelta64 with non-nanosecond resolution Timestamp pd.Timestamp and associated methods labels Dec 23, 2025
@jorisvandenbossche jorisvandenbossche added this to the 3.0 milestone Dec 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

IO JSON read_json, to_json, json_normalize Non-Nano datetime64/timedelta64 with non-nanosecond resolution Timestamp pd.Timestamp and associated methods

Projects

None yet

Milestone

3.0

Development

Successfully merging this pull request may close these issues.

1 participant

@jorisvandenbossche