-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TST: loc misbehaves when Period is at start of 3-level MultiIndex #28628
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
Conversation
Can you add tests specific to parse_time_string. That would go in tests.tslibs.test_parsing |
474cfd8
to
39f90fe
Compare
@jbrockmendel ping? |
d54dc74
to
afd6897
Compare
can you also make sure we have tests for the entire example in the OP (IOW the working cases as well) |
9fedee8
to
d3a70fd
Compare
c1e1e64
to
e67736d
Compare
23783bf
to
f08aafe
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok looks fine, if you'd remove the note, otherwise lgtm. ping on green.
6670997
to
7a70de9
Compare
7a70de9
to
345d779
Compare
thanks @proost |
@jbrockmendel @jreback |
If index is MultiIndex and level of 0 is PeriodIndex, loc function raise
exception if all input of loc does not match index values
Background: This bug only happens when MultiIndex's level is 3 and first level index is PeriodIndex. In this situation, if someone access one row using a '.loc' with a miss match key, then would not raise exception.
Someone already change what i try to do
parse_time_string
function in '_libs.tslibs.parsing'.in the past,
What i try to do:
now in master:
Just add tests for issue.
black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff