[issue1729305] test_doctest fails when run in verbose mode

Florent Xicluna added the comment: And for Python 3. (Slightly different) -- stage: -> patch review Added file: http://bugs.python.org/file15991/issue1729305_doctest_py3k.diff ___ Python tracker ___

[issue1729305] test_doctest fails when run in verbose mode

Florent Xicluna added the comment: The patch did not work with latest trunk. Here is an updated version of the patch. Patch tested with different commands: ~ $ ./python -m test.regrtest test_doctest ~ $ ./python -m test.regrtest -v test_doctest ~ $ ./python -m test.regrtest -v test_doctest |le

[issue1729305] test_doctest fails when run in verbose mode

Florent Xicluna added the comment: It still occurs on trunk. test test_doctest crashed -- : 'ascii' codec can't encode characters in position 343-344: ordinal not in range(128) -- components: +Tests -Library (Lib) nosy: +flox versions: +Python 2.7 ___

[issue1729305] test_doctest fails when run in verbose mode

Ezio Melotti added the comment: This test still fail on Win7 with Py2.6.3rc1 in verbose mode, it works fine in normal mode. I attached a file with the traceback. -- nosy: +ezio.melotti versions: +Python 2.6 -Python 2.5 Added file: http://bugs.python.org/file15102/doctestfail.txt __

[issue1729305] test_doctest fails when run in verbose mode

Mike Beachy added the comment: Here's a patch for test_doctest.py that checks the problem has been fixed. Added file: http://bugs.python.org/file9534/test_doctest.patch _ Tracker <[EMAIL PROTECTED]> __

[issue1729305] test_doctest fails when run in verbose mode

Mike Beachy added the comment: The basic issue here is that running in verbose mode echoes back the expected values from the file, so the results from non-ascii doctest files must be encoded before printing. It looks to me like the DocTestRunner class must grow an '_encoding' attribute to keep t