[issue9409] doctest in python2.7 can't handle non-ascii characters

2010-10-14 Thread Florent Xicluna
Florent Xicluna added the comment: Fixed in 2.7 with r85496 and r85501. Thank you. (in 3.2 only tests, r85495 and r85500) -- resolution: -> fixed stage: unit test needed -> committed/rejected status: open -> closed ___ Python tracker

[issue9409] doctest in python2.7 can't handle non-ascii characters

2010-07-31 Thread Éric Araujo
Éric Araujo added the comment: Adding the release manager to nosy so that he can confirm this bugfix can make it in the next 2.7 release before there’s more effort on that. -- nosy: +benjamin.peterson, merwok ___ Python tracker

[issue9409] doctest in python2.7 can't handle non-ascii characters

2010-07-31 Thread Éric Araujo
Changes by Éric Araujo : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue9409] doctest in python2.7 can't handle non-ascii characters

2010-07-28 Thread Ezio Melotti
Ezio Melotti added the comment: This change has been introduced in r79307 (see #7667). The error seems to be raised because example.source is not unicode so it gets decoded implicitly before getting encoded with ascii+backslashreplace. I don't know if example.source is always supposed to be st

[issue9409] doctest in python2.7 can't handle non-ascii characters

2010-07-28 Thread Hugo Lopes Tavares
Changes by Hugo Lopes Tavares : Added file: http://bugs.python.org/file18244/example.py ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue9409] doctest in python2.7 can't handle non-ascii characters

2010-07-28 Thread Hugo Lopes Tavares
Changes by Hugo Lopes Tavares : Added file: http://bugs.python.org/file18243/non-ascii.txt ___ Python tracker ___ ___ Python-bugs-list mailing

[issue9409] doctest in python2.7 can't handle non-ascii characters

2010-07-28 Thread Hugo Lopes Tavares
New submission from Hugo Lopes Tavares : When trying to run my test suite I had a problem with python2.7. My suite ran 100% in Python2.4, Python2.5, Python2.6 and Python3.2a0, so I thought it would be a kind of doctest flaw. Taking a look at the code, there is the following in doctest.py:1331: