-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
Pandas 1.0.1 fails get_loc on timeindex (0.25.3 works) #32140
Comments
@AndrewMoscoe Thanks for the report! This is already working again on master. But so we should verify it if also works on the 1.0.x branch (to become 1.0.2), or if there is something we need to backport. |
@jorisvandenbossche This bug was noticed in #26683 (comment) and fixed in #31511. so we need to backport that PR. and move the whatsnew. any particular order? Also, do we need to add another test for this? |
The order is not that important. I think the easiest is to backport the PR (can first try asking MeeseeksDev, in case there is no conflict), and update the branch with moving the whatsnew. And then a separate PR moving the whatsnew just in master. I would also still add a test, since the case seems a bit different. |
xref #31964 |
OK will
|
Sounds good, thanks! |
had already cherry-picked locally to test. so just created backport manually. |
Problem description
With pandas 1.0.1, python 3.8.1
With 0.25.3, this returns index location 7433 as expected.
I've tested this on Windows 10 1909, and Ubuntu WSL, and get the same error on both.
Output of
pd.show_versions()
The text was updated successfully, but these errors were encountered: