-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
[BUG] Validate dtype when Int64Index, UInt64Index, or Float64Index are cons… #29545
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Can you add an entry to the 1.0 whatsnew under the "Bug Fixes - Numeric" subsection?
…dtype to be passed to float64index, match valueerror message
Done, but I don't think it's right yet, need to understand what goes on in test_coercion (shouldn't be necessary to allow Float64 index with integer dtype?) UPDATE: fixed |
…ad remove dtype from call to Float64Index in the constructor of Index
@jschendel thanks for your review :) I've updated my PR as per your suggestions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you conform RangeIndex._validate_dtype to the same signature here
Thanks for your reviews, @jreback and @jschendel , really appreciate it. Have updated the PR accordingly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm overall; one small comment
@jschendel sure, done! |
Can you merge master to resolve the conflict in the whatsnew? |
Done - thanks for the approval! |
thanks @MarcoGorelli |
…tructed
dtype
parameter #29539black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff