-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Multiindexing slicing of dates #3843
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
why don't u reset index, subset on the dates and/or id? the problem with selecting via a tuple range is a) index must be sorted and b) the code is complicated with dates mark as a bug for. 0.12 I guess |
Another datetime slicing issue: http://stackoverflow.com/questions/17044808/python-pandas-attributeerror-numpy-ndarray-object-has-no-attribute-start. |
Can't seem to repru the isee you mention in the link just above
|
@hayd I think the example indicated (the pivot) is actually not a bug, but a misuse; you can't slice on labels that are not included in the index, whether date or not (if they ARE STRINGS)
so I guess it is a buglet then; here treating datetimes different from the strings....hmmm |
How fun! (I thought I'd played around with things like that.) |
@hayd close this? or make a bug/enhancement out of it? |
So you can do it with strings, even in a mi, just not when they are dates? Should we pull out that as a someday feature? |
it's a bug/feature just have to track down |
|
Should I be able to slice like follows:
But if I try and slice from outside any of the ranges, I get an exception:
see this SO question.
The text was updated successfully, but these errors were encountered: