On Thu, Sep 17, 2020 at 3:02 PM Wes Turner <wes.tur...@gmail.com> wrote: > > Something like this in the docstring?: "In order to support the historical > JSON specification and closed ecosystem JSON, it is possible to specify an > encoding other than UTF-8." >
I don't think dumpf should support encoding parameter. 1. Output is ASCII unless `ensure_ascii=True` is specified. 2. Writing new JSON file with obsolete spec is not recommended. 3. If user really need it, they can write obsolete JSON by `dump` or `dumps` anyway. I against adding `encoding` parameter to dumpf and loadf. They are just shortcut for common cases. Regards, -- Inada Naoki <songofaca...@gmail.com> _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/7V3UAEBUKYEQDYYJIGJUVW3DYCDDQN46/ Code of Conduct: http://python.org/psf/codeofconduct/
