-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
.loc lookup with missing values #11428
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
I can confirm this, and this does not sound as intentional I think. Using reindex still works as expected:
|
not sure if this is related, but this also looks off. The tests pass when timezones are not used.
|
This looks fixed on master, but as the warning notes this will deprecated in the future.
|
Does this still need unit testing? I'm new to working on pandas and I'm not sure if I'd be doing redundant work here. |
Sure. Feel free to add a unit test for this. |
Hi everyone, I recently upgraded from 0.16.2 to 0.17.0, and I am wondering if this change was intentional:
0.16.2
(numpy version 1.10)
pd version 0.17.0
np version 1.10.1
I realize that 2001-01-14 is not in the index of series s, and I was hoping that .loc would just fill it in as nan. I can understand if it threw a KeyError, but I am now getting a ValueError. Was this change intentional? I checked the docs, but I didn't see it there.
The text was updated successfully, but these errors were encountered: