[issue2811] doctest doesn't treat unicode literals as specified by the file declared encoding

Terry J. Reedy added the comment: In 3.1.2, where the docstring is unicode, the doctest of normalize works fine, as Karen said. I think she is right: without the encoding being explicitly passed to doctest, it cannot affect how the sub-interpreter used by doctest compiles the strings as code.

[issue2811] doctest doesn't treat unicode literals as specified by the file declared encoding

Changes by Éric Araujo : -- nosy: +Merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue2811] doctest doesn't treat unicode literals as specified by the file declared encoding

Karen Tracey <[EMAIL PROTECTED]> added the comment: I believe the problem is in your test file, not doctest. The enclosing doctest string is not specified as a unicode literal, so the file encoding specification ultimately has no effect on it. At least that is how I read the documentation regar

[issue2811] doctest doesn't treat unicode literals as specified by the file declared encoding

New submission from Paulo Eduardo Neves <[EMAIL PROTECTED]>: Doctest doesn't obey the specified file encoding for unicode literals. I've put the minimum test case that demonstrate the error in the attached file. The program has the # -*- coding: utf-8 -*- as the first line and is saved in thi