RetroSearch Browse

Tue Apr 22 23:12:18 CEST 2008 · https://mail.python.org/pipermail/python-dev/2008-April/078816.html

-On [20080418 18:05], Adam Olsen (rhamph at gmail.com) wrote:
>4. Make doctest smarter, so that it can grab the original module's encoding.
>5. Wait until 3.0, where this is hopefully fixed by making doctests
>use unicode by default?

Getting rid of the u in front of the strings as required made Python 3
indeed run the doctests as they should.

So there's a difference in behaviour between 2.x and 3.0 when it comes to
this part. I guess the better behaviour would be for doctest to honour the
encoding specified in the file/module? If other people agree I can see what
I can to make that work.

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Confutatis maledictis, flammis acribus addictis...

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-April/078816.html below:

[Python-Dev] Known doctest bug with unicode?