-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Disallow non-scalar fill_value in maybe_upcast #29362
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
…ybe_upcast_nomask
…ybe_upcast_nomask
this is orthogonal to #29331 ? |
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.
do we need additional tests here?
correct
for maybe_upcast_putmask i dont think so. for Block.shift maybe; im still a little iffy on the object-dtype case there |
thanks, pls followon tests as needed |
Along with #29331 and #29332 this allows us to rule out non-scalar fill_value being passed to maybe_promote for almost all cases, the last few of which we'll have to address individually.
The restriction in
Block.shift
could be an API change if you squint and tilt your head.The assertion in masked_rec_array_to_mgr is based on my read of the numpy docs, but it'd be worth double-checking.