[Python-Dev] failure in test_sre???

Tim Peters tim_one@email.msn.com
Sat, 2 Sep 2000 23:18:31 -0400


[Mark Favas, on new test_sre failures]
> Is it just me, or is test_sre meant to fail, following the recent
> changes to _sre.c?

Checkins are never supposed to leave the test suite in a failing state, but
while that's "the rule" it's still too rarely the reality (although *much*
better than it was just a month ago -- whining works <wink>).  Offhand these
look like shallow new failures to me, related to /F's so-far partial
implemention of PEP 223 (Change the Meaning of \x Escapes).  I'll dig into a
little more.  Rest assured it will get fixed before the 2.0b1 release!

> Short failure message:
> test test_sre failed -- Writing: 'sre.match("\\x%02x" % i, chr(i)) !=
> None', expected: ''
>
> Full failure messages:
> Running tests on character literals
> sre.match("\x%02x" % i, chr(i)) != None FAILED
> Traceback (most recent call last):
>   File "test_sre.py", line 18, in test
>     r = eval(expression)
> ValueError: invalid \x escape
> sre.match("\x%02x0" % i, chr(i)+"0") != None FAILED
> Traceback (most recent call last):
>   File "test_sre.py", line 18, in test
>     r = eval(expression)
> ValueError: invalid \x escape
> sre.match("\x%02xz" % i, chr(i)+"z") != None FAILED
> Traceback (most recent call last):
>   File "test_sre.py", line 18, in test
>     r = eval(expression)
> ValueError: invalid \x escape
>
> (the above sequence is repeated another 7 times)
>
> --
> Mark
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev@python.org
> http://www.python.org/mailman/listinfo/python-dev