-
-
Notifications
You must be signed in to change notification settings - Fork 18k
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
can't obtain items from DatetimeIndex'ed DataFrame #7209
Comments
can u provide a pickle of results? |
On Thu, 22 May 2014, jreback wrote:
sure! FWIW: checked that it loads fine Yaroslav O. Halchenko, Ph.D. |
when i click the link no file is found |
you should be using |
and indeed means is Series... but why such discrimination between the two structures behavior? |
yet, when slicing a time-series based index, the a bit confusing, though can be convient. Its sort of a wart, not really sure what (if anything to do about it). e.g.
Currently
'correct' slicing semantics
|
ah -- somewhat make a sense now ;-) thanks for helping along and unless you would like to do anything about it e.g. some type checking, catching the exception and issuing more meaningful exception or just handling single index entries also legit happen there is no column with Timestamps... -- feel free to close. cheers! |
yeh...this is a very tricky issue....not sure we CAN do much about it |
I was just thinking, there is indeed not much we can do about this (it's also a feature, just one with some inconvenient side-effects), but maybe we can do something about the error message to make it clearer? (I am not sure what is possible here, just suggesting) Eg, it could already be clearer maybe to add the axis where the key is not found: KeyError: u'no item named 2011-03-13 11:39:17 in axis 1' (or 'in the column labels', ..) then it can maybe trigger the 'aha, I am accessing the columns, and not the index as I wanted' |
hmm...ok that is realistic (though it IS a bit tricky to implement)....ok will create an issue for it |
found that my numpy-vbench setup was not working for a while due to need for fresh cython... upgraded cython. Now I am trying to render pages where I got code hitting #4547 but even rebuilding pandas current master ( v0.14.0rc1-51-gccd593f) using cython 0.19.2+git5-g0c6fdf0-1~nd70+1 resulted in the same failure, so I decided to change my code but got stuck with inability to reference entries in the DataFrame using its own index items:
This session is with prev release:
in current master it was similar:
am I doing something stupid or there is a bug somewhere? didn't look into how those timestamps stored in the sqlite DB and brought back -- may be loading/unpickling? them back somehow causes this behavior... just awkward
The text was updated successfully, but these errors were encountered: