BUG: DataFrame constructor should not promote complex64 dtypes (GH10952) #10975
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
very simple! nice! |
jreback
added
Dtype Conversions
|
merged via b5b06cf tip: to avoid merge conflicts in the whatsnew, put the entry not at the end, that's why I leave blank spaces in the Bug fixes (though this is a slight api change). |
|
Thanks! I'll remember to leave spaces in the file next time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses GH10952.
When passing an array with complex64 dtype to the DataFrame constructor, that array will no longer be automatically promoted to the complex128 dtype (different complex dtypes are now allowed).