Commit da9eeae4 authored by Ezio Melotti's avatar Ezio Melotti

#11963: avoid printing messages in test_parser. Initial patch by Éric Araujo.

parent 26e2faf5
......@@ -3,6 +3,7 @@ import unittest
import sys
import struct
from test import test_support as support
from test.script_helper import assert_python_failure
#
# First, we test that we can generate trees from valid source fragments,
......@@ -579,7 +580,7 @@ class CompileTestCase(unittest.TestCase):
class ParserStackLimitTestCase(unittest.TestCase):
"""try to push the parser to/over it's limits.
"""try to push the parser to/over its limits.
see http://bugs.python.org/issue1881 for a discussion
"""
def _nested_expression(self, level):
......@@ -592,8 +593,10 @@ class ParserStackLimitTestCase(unittest.TestCase):
def test_trigger_memory_error(self):
e = self._nested_expression(100)
print >>sys.stderr, "Expecting 's_push: parser stack overflow' in next line"
self.assertRaises(MemoryError, parser.expr, e)
rc, out, err = assert_python_failure('-c', e)
# parsing the expression will result in an error message
# followed by a MemoryError (see #11963)
self.assertEqual(err, b's_push: parser stack overflow\nMemoryError')
class STObjectTestCase(unittest.TestCase):
"""Test operations on ST objects themselves"""
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment