This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients Haoyu SUN, eric.smith, mark.dickinson, rhettinger
Date 2020-05-16.03:36:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1589600181.31.0.50987603252.issue40633@roundup.psfhosted.org>
In-reply-to
Content
[Eric]
> this is documented behavior

[Mark]
> I definitely wouldn't want to see nans translated to 
> "null" by default.

I concur with both of these statements.

I would support adding an option (off by default) to convert NaNs to None.  While NaNs were originally intended to indicate an invalid value, they sometimes get used to denote missing values.  In those situations, it would be reasonable to convert NaN to null.
History
Date User Action Args
2020-05-16 03:36:21rhettingersetrecipients: + rhettinger, mark.dickinson, eric.smith, Haoyu SUN
2020-05-16 03:36:21rhettingersetmessageid: <1589600181.31.0.50987603252.issue40633@roundup.psfhosted.org>
2020-05-16 03:36:21rhettingerlinkissue40633 messages
2020-05-16 03:36:21rhettingercreate