On Aug 12, 2019, at 15:34, Christopher Barker <[email protected]> wrote: > > In fact, I'm pretty sure that setting custom separators the only way to get > it to generate invalid JSON now,
There’s also allow_nan. But that one is clearly intentional, because so many other implementations (including the original JS reference implementation) break the spec in that way that it’s useful to have an option to do the same. (Even without that option, Python raises a ValueError instead of emitting null, but that’s not a way to get invalid JSON, it’s just a way to not get any JSON when the library should have allowed it…) Also, because Python follows the obsolete RFC 7159 instead of 8259, there may be other issues—I don’t think there are, but I wouldn’t want to guarantee that without checking. _______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/DU52ARYQBX5JFU5MITOJ67AWMLUZH5BG/ Code of Conduct: http://python.org/psf/codeofconduct/
