BUG: nunique not ignoring both None and np.nan

doc/source/whatsnew/v1.2.0.rst

@@ -562,6 +562,7 @@ Other
 - Bug in :meth:`Index.union` behaving differently depending on whether operand is a :class:`Index` or other list-like (:issue:`36384`)
 - Passing an array with 2 or more dimensions to the :class:`Series` constructor now raises the more specific ``ValueError``, from a bare ``Exception`` previously (:issue:`35744`)
 - Bug in ``accessor.DirNamesMixin``, where ``dir(obj)`` wouldn't show attributes defined on the instance (:issue:`37173`).
+- Bug in :meth:`nunique` with ``dropna = True`` returns wrong result when different kinds of NA-like values exist (:issue:`37566`)
 
 .. ---------------------------------------------------------------------------
 

pandas/core/base.py

@@ -1032,10 +1032,11 @@ def nunique(self, dropna: bool = True) -> int:
         >>> s.nunique()
         4
         """
-        uniqs = self.unique()
+        if dropna:
+            uniqs = self.dropna().unique()
+        else:
+            uniqs = self.unique()
         n = len(uniqs)
-        if dropna and isna(uniqs).any():
-            n -= 1
         return n
 
     @property

pandas/tests/base/test_unique.py

@@ -121,3 +121,11 @@ def test_unique_bad_unicode(idx_or_series_w_bad_unicode):
     else:
         expected = np.array(["\ud83d"], dtype=object)
         tm.assert_numpy_array_equal(result, expected)
+
+
+def test_nunique_dropna():
+    # test for #37566
+    s = pd.Series(['yes', 'yes', pd.NA, np.nan, None, pd.NaT])
+    res = s.nunique(dropna=True)
+    expected = 1
+    assert res == expected