➜

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 mark.dickinson
Recipients Haoyu SUN, arjanstaring, eric.smith, mark.dickinson, rhettinger
Date 2020-11-20.18:06:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1605895595.88.0.448206963884.issue40633@roundup.psfhosted.org>
In-reply-to
Content 
@Arjan Staring: could you point to which part of the JSON specification you're looking at?

At https://tools.ietf.org/html/rfc7159, the only reference to NaNs that I see is:

> Numeric values that cannot be represented in the grammar below (such
> as Infinity and NaN) are not permitted.

At https://www.json.org/json-en.html, there's no mention of IEEE 754 special values.

I'm not seeing anything anywhere to suggest that the JSON specification says NaNs should be translated to nulls.
History
Date User Action Args
2020-11-20 18:06:35mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, eric.smith, Haoyu SUN, arjanstaring
2020-11-20 18:06:35mark.dickinsonsetmessageid: <1605895595.88.0.448206963884.issue40633@roundup.psfhosted.org>
2020-11-20 18:06:35mark.dickinsonlinkissue40633 messages
2020-11-20 18:06:35mark.dickinsoncreate