We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
in the 1.40rc1 release notes: https://pandas.pydata.org/pandas-docs/version/1.4/whatsnew/v1.4.0.html#null-values-are-no-longer-coerced-to-nan-value-in-value-counts-and-mode
We are seeing distinct NaN , but I think we should be seeing NaN and NaT
NaN
NaT
Looks like we patched here: #42743
The text was updated successfully, but these errors were encountered:
cc @realead if you can
Sorry, something went wrong.
@jreback Sorry I didn't pay the needed attention to the output and overlooked that when a series is printed all null-values are printed as NaN, i.e.:
import pandas as pd import numpy as np s=pd.Series([1, 2, 3, 4], [True, None, np.nan, pd.NaT])
and now
print(s.keys()) print(s[np.nan])
work as expected:
Index([True, None, nan, NaT], dtype='object') 3
but
print(s)
yields:
True 1 NaN 2 NaN 3 NaN 5
i.e. all NaNs.
For the documentation it is probably better to create another example.
But is this the behavior of series one would like to have/expect with print?
print
I think this issue is closed via #45283
Successfully merging a pull request may close this issue.
in the 1.40rc1 release notes: https://pandas.pydata.org/pandas-docs/version/1.4/whatsnew/v1.4.0.html#null-values-are-no-longer-coerced-to-nan-value-in-value-counts-and-mode
We are seeing distinct
NaN
, but I think we should be seeingNaN
andNaT
Looks like we patched here: #42743
The text was updated successfully, but these errors were encountered: