-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BUG: Timestamp.isoformat works incorrect on ns precision #53020
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.
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
Comments
i1oveMyse1f
added a commit
to i1oveMyse1f/pandas
that referenced
this issue
May 1, 2023
i1oveMyse1f
added a commit
to i1oveMyse1f/pandas
that referenced
this issue
May 4, 2023
i1oveMyse1f
added a commit
to i1oveMyse1f/pandas
that referenced
this issue
May 9, 2023
i1oveMyse1f
added a commit
to i1oveMyse1f/pandas
that referenced
this issue
May 9, 2023
mroeschke
pushed a commit
that referenced
this issue
May 9, 2023
Rylie-W
pushed a commit
to Rylie-W/pandas
that referenced
this issue
May 19, 2023
* fix pandas-dev#53020 * add tests pandas-dev#53020
Daquisu
pushed a commit
to Daquisu/pandas
that referenced
this issue
Jul 8, 2023
* fix pandas-dev#53020 * add tests pandas-dev#53020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pandas version checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
Issue Description
If the requested precision is in nanoseconds and the timestamp has 0 microseconds, then the format is invalid and looks like the following:
2023-01-01T00:00:00.000000.000000000
2023-01-01T00:00:00.000000.000000001
Expected Behavior
2023-01-01T00:00:00.000000000
2023-01-01T00:00:00.000000001
Installed Versions
The text was updated successfully, but these errors were encountered: