-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
"is_all_dates" inconsistent across datetimelike types #19204
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
this should be made more like the other |
I'm a newbie here and I'm in search of fun! Can I help you with that? =) |
@gilbertoolimpio yep, that'd be great. Do you know where to start? |
I suggest then to just deprecate it, since it becomes equivalent to a simple |
…) - improved tests, removed unnecessary imports
…) - improved tests, removed unnecessary imports
…) - improved tests, removed unnecessary imports
…) - fixed code formatting
closed by #36697 |
xref #19187
Code Sample, a copy-pastable example if possible
Problem description
is_all_dates
is smart forobject
indexes but only forDatetimeIndex
, which is inconsistent since the other datetimelike indexes are also consideredis_all_dates
.Expected Output
Out[5]:
andOut[6]:
should be the same asOut[3]:
.Output of
pd.show_versions()
[paste the output of
pd.show_versions()
here below this line]The text was updated successfully, but these errors were encountered: