-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG/API: Clarify the behaviour of fillna downcasting #11537
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
Comments
floats are never downcast by default |
Thanks. Is the following correct? If so, I'll include it to the document in #11497.
Based on the last condition, this should result in
|
@sinhrks IIRC that looks right. yeah it is meant for explicit use. though to be honest maybe we should just take this out and always downcast |
From #11497. Found inconsistencyr regarding
fillna
downcasting.I understand
fillna(downcast=None)
should downcast values appropriately. It doesn't work onfloat
dtype.Based on the internal logic,
downcast
can accept dtype. It works onfloat
, but not onobject
.I understood the expected behavior as below:
downcast
kw, downcast to the specified dtype if possible.downcast=False
will not perform downcast.Index.fillna
to API (follow-up of ENH: Add Index.fillna #11343)The text was updated successfully, but these errors were encountered: