-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Question/bug: How to get rid of "0 days" in timedelta64[s] #35463
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
Thanks @pllim for the report. Not sure if this was an intentional change, so will mark as regression pending further investigation. |
It appears this was an intentional change, see tests changed in #33270 |
Wasn't expecting that in a minor release. Is there a way to get the old behavior back? If no, that's fine too, just want to know. |
minor release can and do have api changes - pls read the release notes this was for conformity of timedelta outputs |
I did glance at the notes but I guess I missed it. Okie dokie then. |
Thanks for digging into this, @simonjayhawkins ! |
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas. -- I can't tell if this is a feature or a bug.
(optional) I have confirmed this bug exists on the master branch of pandas.
Note: Please read this guide detailing how to provide the necessary information for us to reproduce your bug.
Code Sample, a copy-pastable example
Problem description
"0 days" started to appear when DataFrame contains
timedelta64[s]
.Expected Output
See "Code Sample" for
pandas
1.0.5.Output of
pd.show_versions()
See "Code Sample" for
pandas
1.1.0.Further readings
astropy/astropy#10608 and astropy/astropy#10609
The text was updated successfully, but these errors were encountered: