diff options
| author | Jason Thai <jasonnthaii@gmail.com> | 2022-05-29 00:49:19 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-05-29 00:49:19 -0700 |
| commit | 350b3fe83ff48bb9b87e06e8b1c0be6072141f39 (patch) | |
| tree | 7582f02279518d9d99d900f1ab21eb2ce4e965ac /doc | |
| parent | 345ced482bac1c974d6bc8b70b101293d76a16e1 (diff) | |
| download | numpy-350b3fe83ff48bb9b87e06e8b1c0be6072141f39.tar.gz | |
DOC: Update 21623 release documentation
Co-authored-by: Matti Picus <matti.picus@gmail.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release/upcoming_changes/21623.new_feature.rst | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/release/upcoming_changes/21623.new_feature.rst b/doc/release/upcoming_changes/21623.new_feature.rst index 33e86ad26..fafb2e8d6 100644 --- a/doc/release/upcoming_changes/21623.new_feature.rst +++ b/doc/release/upcoming_changes/21623.new_feature.rst @@ -1,4 +1,6 @@ New parameter ``equal_nans`` added to `np.unique` ----------------------------------------------------------------------------------- -`np.unique` was previously changed to treat NaN values as equal. Now this functionality is decided by setting the ``equal_nans`` kwarg to True or False. True is the default behavior. +`np.unique` was changed in 1.21 to treat all ``NaN`` values as equal and return +a single ``NaN``. Setting ``equal_nans=False`` will restore pre-1.21 behavior +to treat ``NaNs`` as unique. Defaults to ``True``. |