Skip to content

BUG: Bug in setting complex dtypes via boolean indexing (GH6345) #6347

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
Feb 14, 2014

Conversation

jreback
Copy link
Contributor

@jreback jreback commented Feb 13, 2014

closes #6345

@jreback jreback added this to the 0.14.0 milestone Feb 13, 2014
# GH 6345
expected = DataFrame([[1+1j, 2], [np.nan, 4+1j]], columns=['a', 'b'])
df = DataFrame([[1+1j, 2], [5+1j, 4+1j]], columns=['a', 'b'])
import pdb; pdb.set_trace()
Copy link
Contributor

Choose a reason for hiding this comment

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

oops

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yep

jreback added a commit that referenced this pull request Feb 14, 2014
BUG: Bug in setting complex dtypes via boolean indexing (GH6345)
@jreback jreback merged commit ee43575 into pandas-dev:master Feb 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Dtype Conversions Unexpected or buggy dtype conversions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

inplace where with complex column changes dtype to float
2 participants