[ python-Bugs-1076790 ] test test_codecs failed
SourceForge.net
noreply at sourceforge.net
Wed Dec 1 18:20:57 CET 2004
Bugs item #1076790, was opened at 2004-12-01 15:41
Message generated for change (Comment added) made by lemburg
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1076790&group_id=5470
Category: Python Library
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Michal Čihař (nijel)
Assigned to: Nobody/Anonymous (nobody)
Summary: test test_codecs failed
Initial Comment:
test test_codecs failed -- Traceback (most recent call
last):
File
"/usr/src/packages/BUILD/Python-2.4/Lib/test/test_codecs.py",
line 446, in test_nameprep
raise test_support.TestFailed("Test 3.%d: %s" %
(pos+1, str(e)))
TestFailed: Test 3.5: u'\u0143 \u03b9' != u'\u0144 \u03b9'
----------------------------------------------------------------------
>Comment By: M.-A. Lemburg (lemburg)
Date: 2004-12-01 18:20
Message:
Logged In: YES
user_id=38388
Ah, now I understand: it is well possible that the Unicode
database versions differ. Python uses version 3.2.
Do you know which version glibc 2.3.3 uses ?
Note that for portability it is usually better not to use wctype
functions.
----------------------------------------------------------------------
Comment By: Michal Čihař (nijel)
Date: 2004-12-01 17:32
Message:
Logged In: YES
user_id=192186
The problem seems to be in glibc, when I remove
--with-wctype-functions, it passes. Or could it be in Python
interface to wctype functions?
----------------------------------------------------------------------
Comment By: Michal Čihař (nijel)
Date: 2004-12-01 17:21
Message:
Logged In: YES
user_id=192186
gcc (GCC) 3.3.4 (pre 3.3.5 20040809)
Yes, I'm building UCS4 version.
----------------------------------------------------------------------
Comment By: M.-A. Lemburg (lemburg)
Date: 2004-12-01 17:16
Message:
Logged In: YES
user_id=38388
Sorry: I misread glibc as gcc. Still, this sounds a lot like
a broken compiler.
BTW, are you building a UCS4 version ?
----------------------------------------------------------------------
Comment By: M.-A. Lemburg (lemburg)
Date: 2004-12-01 17:15
Message:
Logged In: YES
user_id=38388
The tests pass just fine on my machine.
Is it possible that your compiler is broken ?
gcc 2.3.3 is *very* old !
----------------------------------------------------------------------
Comment By: Michal Čihař (nijel)
Date: 2004-12-01 16:26
Message:
Logged In: YES
user_id=192186
System information:
i386
kernel 2.6.8
glibc 2.3.3
----------------------------------------------------------------------
Comment By: Michal Čihař (nijel)
Date: 2004-12-01 15:59
Message:
Logged In: YES
user_id=192186
It's clean build root with no other python, so it has no
chance to pickup bad modules.
----------------------------------------------------------------------
Comment By: M.-A. Lemburg (lemburg)
Date: 2004-12-01 15:53
Message:
Logged In: YES
user_id=38388
Please make sure that Python is picking up the correct modules.
You can do so, buy running Python in verbose mode (python -vv).
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1076790&group_id=5470
More information about the Python-bugs-list
mailing list