-
-
Notifications
You must be signed in to change notification settings - Fork 18.3k
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
check early for non-scalar default_fill_value #27302
Conversation
@@ -74,6 +75,8 @@ def __init__( | |||
dtype=None, | |||
copy=False, | |||
): | |||
if not is_scalar(default_fill_value): |
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.
Is a dict acceptable here at all? Think we allow that for normal DataFrame fillna
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.
@TomAugspurger are there cases where non-scalar is accepted? I was getting errors in another branch caused by zero-dim ndarray getting through here.
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.
I don't believe we allow this (nor should)
Co-Authored-By: Simon Hawkins <[email protected]>
is there an issue for this? I guess currently this raises but its an incorrect description of the error? |
ATM this raises once it gets passed to SparseArray. The actual bug this fixes is the |
thanks |
Broken off of an in-progress division-by-zero branch