summaryrefslogtreecommitdiffstats
path: root/Lib/test/crashers/recursion_limit_too_high.py
diff options
context:
space:
mode:
Diffstat (limited to 'Lib/test/crashers/recursion_limit_too_high.py')
-rw-r--r--Lib/test/crashers/recursion_limit_too_high.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/Lib/test/crashers/recursion_limit_too_high.py b/Lib/test/crashers/recursion_limit_too_high.py
index 1fa4d32..ec64936 100644
--- a/Lib/test/crashers/recursion_limit_too_high.py
+++ b/Lib/test/crashers/recursion_limit_too_high.py
@@ -5,7 +5,7 @@
# file handles.
# The point of this example is to show that sys.setrecursionlimit() is a
-# hack, and not a robust solution. This example simply exercices a path
+# hack, and not a robust solution. This example simply exercises a path
# where it takes many C-level recursions, consuming a lot of stack
# space, for each Python-level recursion. So 1000 times this amount of
# stack space may be too much for standard platforms already.