-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
PDEP-11: Change default of dropna to False #53094
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
base: main
Are you sure you want to change the base?
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,78 @@ | ||
# PDEP-11: dropna default in pandas | ||
|
||
- Created: 4 May 2023 | ||
- Status: Under discussion | ||
- Discussion: [PR #53094](https://github.com/pandas-dev/pandas/pull/53094) | ||
- Authors: [Richard Shadrach](https://github.com/rhshadrach) | ||
- Revision: 1 | ||
|
||
## Abstract | ||
|
||
Throughout pandas, almost all of the methods that have a `dropna` argument default | ||
to `True`. Being the default, this can cause NA values to be silently dropped. | ||
This PDEP proposes to deprecate the current default value of `True` and change it | ||
to `False` in the next major release of pandas. | ||
|
||
## Motivation and Scope | ||
|
||
Upon seeing the output for a Series `ser`: | ||
|
||
```python | ||
print(ser.value_counts()) | ||
|
||
1 3 | ||
2 1 | ||
dtype: Int64 | ||
``` | ||
|
||
users may be surprised that the Series can contain NA values. By then operating | ||
on data under the assumption NA values are not present, erroroneous results can | ||
arise. The same issue can occur with `groupby`, which can also be used to produce | ||
detailed summary statistics of data. We think it is not unreasonable that an | ||
experienced pandas user seeing the code | ||
|
||
df[["a", "b"]].groupby("a").sum() | ||
|
||
would describe this operation as something like the following. | ||
|
||
> For each unique value in column `a`, compute the sum of corresponding values | ||
> in column `b` and return the results in a DataFrame indexed by the unique | ||
> values of `a`. | ||
|
||
This is correct, except that NA values in the column `a` will be dropped from | ||
the computation. That pandas is taking this additional step in the computation | ||
is not apparent from the code, and can surprise users. | ||
|
||
## Detailed Description | ||
|
||
We propose to deprecate the current default of `dropna` and change it to | ||
`False` across all applicable methods. The following methods have a dropna | ||
argument, those marked with a `*` already default to `False`. | ||
|
||
```python | ||
Series.groupby | ||
Series.mode | ||
Series.nunique | ||
Series.to_hdf* | ||
Series.value_counts | ||
DataFrame.groupby | ||
DataFrame.mode | ||
DataFrame.nunique | ||
DataFrame.pivot_table | ||
DataFrame.stack | ||
DataFrame.to_hdf* | ||
DataFrame.value_counts | ||
SeriesGroupBy.nunique | ||
SeriesGroupBy.value_counts | ||
DataFrameGroupBy.nunique | ||
DataFrameGroupBy.value_counts | ||
``` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think you might be missing a couple functions here.
I think the missing ones are |
||
|
||
## Timeline | ||
|
||
If accepted, the current `dropna` default would be deprecated as part of pandas | ||
2.x and this deprecation would be enforced in pandas 3.0. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How would users find out about this deprecation? I'm concerned it will create noisy messages. For example, if you were to do So can you be more specific about how the deprecation would work? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Added. A warning would only be emitted when |
||
|
||
## PDEP History | ||
|
||
- 4 May 2023: Initial draft |
Uh oh!
There was an error while loading. Please reload this page.