Skip to content

DOC: clarify pitfalls of NA vs NaN in nullable floats #51383

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.

Sign up for GitHub

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

Closed
wants to merge 2 commits into from
Closed

DOC: clarify pitfalls of NA vs NaN in nullable floats #51383

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
24008fa
add note to docstring re NA vs NaN
a-reich Feb 14, 2023
ead6e86
revise docstring per feedback
a-reich Feb 22, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions pandas/core/generic.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7872,6 +7872,14 @@ def isna(self: NDFrameT) -> NDFrameT:
Everything else gets mapped to False values. Characters such as empty
strings ``''`` or :attr:`numpy.inf` are not considered NA values
(unless you set ``pandas.options.mode.use_inf_as_na = True``).
Note: For :class:`FloatingArray` and float-type
:class:`ArrowExtensionArray` the behavior is different, as they
use a mask (represented as pd.NA values) to designate missing
data but can also hold NaN which will **not** get mapped to True
(these values can be detected by :func:`numpy.isnan`).
Users may find this behavior unintuitive and want to
avoid these dtypes if they prefer to have only one
type of missing/NA value.

Returns
-------
Expand Down