This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients lukasz.langa, r.david.murray, the_isz
Date 2011-03-18.17:25:35
SpamBayes Score 1.929404e-06
Marked as misclassified No
Message-id <1300469137.73.0.460418389825.issue11597@psf.upfronthosting.co.za>
In-reply-to
Content
>>> str(u"\u0411")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeEncodeError: 'ascii' codec can't encode character u'\u0411' in position 0: ordinal not in range(128)

So, clearly configparser in 2.x doesn't support unicode.  Now the question is, is this a bug or would adding support be a feature? (If the latter it can't be fixed in 2.7.)  I'll leave the answer to that question up to Lucaz.
History
Date User Action Args
2011-03-18 17:25:37r.david.murraysetrecipients: + r.david.murray, lukasz.langa, the_isz
2011-03-18 17:25:37r.david.murraysetmessageid: <1300469137.73.0.460418389825.issue11597@psf.upfronthosting.co.za>
2011-03-18 17:25:35r.david.murraylinkissue11597 messages
2011-03-18 17:25:35r.david.murraycreate