Skip to content

BUG: disallow mixed dtype operations in eval/query #6652

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 17, 2014
Merged

BUG: disallow mixed dtype operations in eval/query #6652

merged 1 commit into from
Mar 17, 2014

Conversation

cpcloud
Copy link
Member

@cpcloud cpcloud commented Mar 16, 2014

closes #5198

@@ -136,6 +136,8 @@ API Changes
- A tuple passed to ``DataFame.sort_index`` will be interpreted as the levels of
the index, rather than requiring a list of tuple (:issue:`4370`)

- Fix a bug where invalid operations would blow the stack (:issue:`5198`)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe indicate this is for eval/query

@cpcloud
Copy link
Member Author

cpcloud commented Mar 17, 2014

@jreback u ok with this?

@jreback
Copy link
Contributor

jreback commented Mar 17, 2014

yup ok

cpcloud added a commit that referenced this pull request Mar 17, 2014
…ype-operations

BUG: disallow mixed dtype operations in eval/query
@cpcloud cpcloud merged commit 25506e5 into pandas-dev:master Mar 17, 2014
@cpcloud cpcloud deleted the gh-5198-stack-blow-eval-mixed-type-operations branch March 17, 2014 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: recursion limit on eval when operating on different types
2 participants