Message368959
I don't think "null" in JSON is supposed to represent "Not a Number"; it's closer in meaning to Python's `None`. I definitely wouldn't want to see nans translated to "null" by default.
This also only seems to address a part of the issue: what's the proposed action for "Infinity" and "-Infinity"? We've written internal code to deal with float special values in JSON a few times (usually to work with databases that stick to the strict JSON definition), and that code has to find a way to deal with all three of the special values. |
|
Date |
User |
Action |
Args |
2020-05-15 16:54:35 | mark.dickinson | set | recipients:
+ mark.dickinson, eric.smith, Haoyu SUN |
2020-05-15 16:54:35 | mark.dickinson | set | messageid: <1589561675.58.0.629288507557.issue40633@roundup.psfhosted.org> |
2020-05-15 16:54:35 | mark.dickinson | link | issue40633 messages |
2020-05-15 16:54:35 | mark.dickinson | create | |
|