Skip to content

ENH: define the order of resolution for index vs columns in query/eval #6677

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

Merged
merged 1 commit into from
Mar 21, 2014
Merged

ENH: define the order of resolution for index vs columns in query/eval #6677

merged 1 commit into from
Mar 21, 2014

Conversation

cpcloud
Copy link
Member

@cpcloud cpcloud commented Mar 21, 2014

closes #6676

@jreback jreback added this to the 0.14.0 milestone Mar 21, 2014
@jreback
Copy link
Contributor

jreback commented Mar 21, 2014

looks good

cpcloud added a commit that referenced this pull request Mar 21, 2014
ENH: define the order of resolution for index vs columns in query/eval
@cpcloud cpcloud merged commit c12166f into pandas-dev:master Mar 21, 2014
@cpcloud cpcloud deleted the index-resolvers-after-columns branch March 21, 2014 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Define and document the order of index names vs column names in query eval
2 participants