You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 10, 2024. It is now read-only.
I don't feel that strongly one way or the other but there's definitely a case to be made that [36] should be NA. The number of bug reports indicate that at minimum, people get tripped up by this, xref pandas-dev/pandas#9422
So could consider modifying the identity concept for pandas 2.0, since there will be less binding to numpy semantics.
The text was updated successfully, but these errors were encountered:
potentially related to #9
numpy ufuncs have an identity, which
pandas
follows with respect to misssing data.I don't feel that strongly one way or the other but there's definitely a case to be made that
[36]
should beNA
. The number of bug reports indicate that at minimum, people get tripped up by this, xref pandas-dev/pandas#9422So could consider modifying the identity concept for pandas 2.0, since there will be less binding to numpy semantics.
The text was updated successfully, but these errors were encountered: