Benjamin Peterson [EMAIL PROTECTED] added the comment:
*testing stack overflow:* maybe?
--
nosy: +benjamin.peterson
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2555
__
Jean Brouwers [EMAIL PROTECTED] added the comment:
Don't change that line. It is obviously clear already, if someone does
read it. I obviously did not.
/Jean
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2555
__
Changes by Benjamin Peterson [EMAIL PROTECTED]:
--
resolution: - invalid
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2555
__
___
New submission from Jean Brouwers [EMAIL PROTECTED]:
For 32-bit Python 2.6a2 on Solaris 10 (Opteron) built with the SUN C
compiler this test_parser failure does not show up in the summary.
...
test_parser
Expecting 's_push: parser stack overflow' in next line
s_push: parser stack overflow
...
Martin v. Löwis [EMAIL PROTECTED] added the comment:
This is not a bug. How should we phrase the first line to make that
unobviously clear?
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2555
__
