-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
ENH: support coordinate access for indexing #7138
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
Well, there's not much I can fancy doing to overload getitem:
With the second option being a syntactic variation of the first, I take it you have something like the third one in mind. I would prefer something like that, too: it's lengthier yet a lot more flexible (e.g. would allow combining coord and non-coord lookups). In fact, I proposed something like that a while ago in #6328, but that didn't seem to get public appeal. |
@immerrr I remember that issue, but I didn't look in detail hah! so if we were to expand/add to I am wondering how complicated this would get |
Converting spelled-out look ups to numpy flavour should not be, but supporting such numpy lookups in BlockManager code could. |
I don't think we need to be a slave to numpy |
As long as pandas containers are built on top of |
no, what i mean is fundamentally pandas is much more flexible, so we have to have a more general soln to things like indexing (which means its more complicated). Since already support |
This is the maybe ought to just turn this into an indexer
|
we have lookup, i think this can be closed |
df.iloc[[0,1],[0,1]]
means return the square 0-1 rows and 0-1 columnsmight be nice to have a way to mean return the coordinates
(0,0),(0,1)
related #7522
http://stackoverflow.com/questions/23686561/slice-a-pandas-dataframe-by-an-array-of-indices-and-column-names/23686855#23686855
The text was updated successfully, but these errors were encountered: