[Python-Dev] Nasty new bug in test_longexp (original) (raw)
Tim Peters tim_one@email.msn.com
Tue, 15 Aug 2000 23:23:44 -0400
- Previous message: [Python-Dev] Fate of Include/my*.h
- Next message: [Python-Dev] socket module changes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Fred, I vaguely recall you touched something here recently, so you're top o' the list. Smells like an uninitialized variable.
1 of 4: test_longexp fails in release build:
C:\PCbuild>python ..\lib\test\regrtest.py test_longexp test_longexp test test_longexp failed -- Writing: '\012', expected: ' ' 1 test failed: test_longexp
2 of 4: but passes in verbose mode, despite that the output doesn't appear to match what's expected (missing " (line 1)"):
C:\PCbuild>python ..\lib\test\regrtest.py -v test_longexp test_longexp test_longexp Caught SyntaxError for long expression: expression too long 1 test OK.
3 of 4: but passes in debug build:
C:\PCbuild>python_d ..\lib\test\regrtest.py test_longexp Adding parser accelerators ... Done. test_longexp 1 test OK. [3962 refs]
4 of 4: and verbose debug output does appear to match what's expected:
C:\PCbuild>python_d ..\lib\test\regrtest.py -v test_longexp
Adding parser accelerators ... Done. test_longexp test_longexp Caught SyntaxError for long expression: expression too long (line 1) 1 test OK. [3956 refs]
C:\PCbuild>
- Previous message: [Python-Dev] Fate of Include/my*.h
- Next message: [Python-Dev] socket module changes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]