On 2013-04-19, Chris ???Kwpolska??? Warrick <kwpol...@gmail.com> wrote:
> On Fri, Apr 19, 2013 at 4:54 PM, Grant Edwards <invalid@invalid.invalid>
> wrote:
>> On 2013-04-18, Wayne Werner <wa...@waynewerner.com> wrote:
>>> On Wed, 17 Apr 2013, Miki Tebeka wrote:
>>>
>>>>>> I'm trying to find a way to have json emit float('NaN') as 'N/A'.
>>>>> No. There is no way to represent NaN in JSON. It's simply not part of
>>>>> the
>>>>> specification.
>>>> I know that. I'm trying to emit the *string* 'N/A' for every NaN.
>>>
>>> Why not use `null` instead? It seems to be semantically more similar...
>>
>> Why not use 'NaN' instead? It seems to be even more semantically
>> similar...
>
> Because there is no NaN in JSON? Unless you mean a string, which
> makes no semantical sense and is human-oriented and not
> machine-oriented.
The OP asked for a string, and I thought you were proposing the string
'null'. If one is to use a string, then 'NaN' makes the most sense,
since it can be converted back into a floating point NaN object.
I infer that you were proposing a JSON null value and not the string
'null'?
--
Grant Edwards grant.b.edwards Yow! I'm receiving a coded
at message from EUBIE BLAKE!!
gmail.com
--
http://mail.python.org/mailman/listinfo/python-list
