[issue9411] configparser doesn't support specifying encoding in read()

Georg Brandl added the comment: Applied in r83220. The **kwds change for some methods should be done separately. -- resolution: -> accepted status: open -> closed ___ Python tracker _

[issue9411] configparser doesn't support specifying encoding in read()

Eric Smith added the comment: The feature request seems reasonable to me, too. I don't recall if sys.getdefaultencoding() can change while a program is running. If so, you might want to change: def read(self, filenames, encoding=sys.getdefaultencoding()): to: def read(self, filenames, encod

[issue9411] configparser doesn't support specifying encoding in read()

Michael Foord added the comment: Seems good to me (the feature - and also the patch after a cursory read through). -- ___ Python tracker ___

[issue9411] configparser doesn't support specifying encoding in read()

Łukasz Langa added the comment: Patch included. -- components: +Library (Lib) keywords: +patch type: -> feature request versions: +Python 3.2 Added file: http://bugs.python.org/file18248/issue9411.diff ___ Python tracker

[issue9411] configparser doesn't support specifying encoding in read()

New submission from Łukasz Langa : By default, configparser classes simply `open()` and `read()` files specified in the list passed to `.read()`. This means these calls use the default platform-specific encoding and this is prone to breakage. An existing solution is to use `readfp()` and pass