homepage

Just what it says on the label :
[...]
Traceback (most recent call last):
 File "./Lib/test/regrtest.py", line 618, in runtest_inner
 indirect_test()
 File
"/home/Pif/Téléchargement/Python-3.1.1/Python-3.1.1/Lib/test/test_cmd_l
 test.support.run_unittest(CmdLineTest)
 File
"/home/Pif/Téléchargement/Python-3.1.1/Python-3.1.1/Lib/test/support.py
 _run_suite(suite)
 File
"/home/Pif/Téléchargement/Python-3.1.1/Python-3.1.1/Lib/test/support.py
 raise TestFailed(err)
test.support.TestFailed: Traceback (most recent call last):
 File
"/home/Pif/Téléchargement/Python-3.1.1/Python-3.1.1/Lib/test/test_cmd_l
 self.assertTrue(path1.encode('ascii') in stdout)
AssertionError: False is not True
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
 File "./Lib/test/regrtest.py", line 1222, in <module>
 main()
 File "./Lib/test/regrtest.py", line 425, in main
 testdir, huntrleaks)
 File "./Lib/test/regrtest.py", line 584, in runtest
 testdir, huntrleaks)
 File "./Lib/test/regrtest.py", line 638, in runtest_inner
 print("test", test, "failed --", msg)
UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in
position 54: ordinal not in range(128)
test test_cmd_line failed -- make: *** [test] Erreur 1
[...]
In my search for similar bugs, I only found a mac OSX/Python 3.0 issue
(http://bugs.python.org/issue4388)

Does it happen if you build python from a directory with no accented
letters?

Nope.
2009年8月21日 Amaury Forgeot d'Arc <report@bugs.python.org>
>
> Amaury Forgeot d'Arc <amauryfa@gmail.com> added the comment:
>
> Does it happen if you build python from a directory with no accented
> letters?
>
> ----------
> nosy: +amaury.forgeotdarc
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue6753>
> _______________________________________
>

Is this still an issue?

A lot of bugs related to encodings has been fixed. The bug was seen on Python 3.1, whereas the current development version is 3.3. We have a Fedora buildbot and many Fedora users, none reported such error recently. I consider this issue as fixed.