-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
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
BUG: .map
& .apply
would convert element type for extension array.
#60766
Comments
Thanks for the report! This is due to #55058, but I don't see much discussion there nor issues that change closes. It does seem surprising to me that one gets |
Agreed this looks strange - the function should be receiving the arguments as integers / pd.NA |
take |
@rhshadrach - What method are you referring on BaseMaskedArray to be removed? Thanks |
|
…tension array. The Int32Dtype type allows representing integers with support for null values (pd.NA). However, when using .map(f) or .apply(f), the elements passed to f are converted to float64, and pd.NA is transformed into np.nan. This happens because .map() and .apply() internally use numpy, which automatically converts the data to float64, even when the original type is Int32Dtype. The fix (just remove the method to_numpy()) ensures that when using .map() or .apply(), the elements in the series retain their original type (Int32, Float64, boolean, etc.), preventing unnecessary conversions to float64 and ensuring that pd.NA remains correctly handled.
Pandas version checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
Issue Description
s
has dtypeInt32Dtype
which can encode nullable integersHowever, when we use
.apply(f)
or.map(f)
, the element passed tof
becomes float, andpd.NA
becomesnp.nan
Expected Behavior
f
should receive unconverted value, as if we are doingf(s.iloc[0])
,f(s.iloc[1])
, ...Installed Versions
tested with Pandas 2.2.3
The text was updated successfully, but these errors were encountered: