-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
API/ENH: enable boolean indexing conditions to reference its input frame via eval #5501
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
@cpcloud might be interesting |
When I posted on stackoverflow I was thinking of a "magic" character/name that would stand for the parent object. eg having '_'stand for the object upon which the method is called. Often in my usage the object is an unnamed series. The eval syntax works when the calling object is a DataFrame and the columns have names that can be intuited from the previous action, but an unnamed series has no name. |
I seem to be missing these kinds of things....guess I should look at the "mentioning you" more often... @jreback sorry about that |
ha! though I think needs some thinking about |
sure but then I'll bet people would want it for regular usage (non query/eval) prob a reasonable idea though |
oh i c now u wanted to have string input used in query and whatever the query was eval it on the caller |
but that happens anyway ... you can chain as much as you want, but you must refer to either cols or locals |
hmm, can now do this by using |
closed by #12539 |
http://stackoverflow.com/questions/19938734/is-there-a-simple-way-to-reference-the-current-object-after-applying-a-chain-of
so could process the condition via an 'eval' type of operation
The text was updated successfully, but these errors were encountered: