On Wed, Sep 16, 2020 at 2:53 PM Wes Turner <wes.tur...@gmail.com> wrote:
> So I was not correct: dump does not default to UTF-8 (and does not accept > an encoding= parameter) > > >> I think dumpf() should use UTF-8, and that's it. If anyone really wants >> something else, they can get it by providing an open text file object. >> > > Why would we impose UTF-8 when the spec says UTF-8, UTF-16, or UTF-32? > The idea was that the encoding was one of the motivators to doing this in the first place. But I suppose as long as utf-8 is the default, and only the three "official" ones are allowed, then yeah, we could add an encoding keyword argument. -CHB -- Christopher Barker, PhD Python Language Consulting - Teaching - Scientific Software Development - Desktop GUI and Web Development - wxPython, numpy, scipy, Cython
_______________________________________________ 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/O73WZF6JKME2VPVWOWYRVQ3APVEA2J5V/ Code of Conduct: http://python.org/psf/codeofconduct/
