summaryrefslogtreecommitdiff
path: root/Doc/lib
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2000-08-31 19:35:56 +0000
committerFred Drake <fdrake@acm.org>2000-08-31 19:35:56 +0000
commit65faf118b61a14caac332d9f44100502b34b7f98 (patch)
tree631e9b2da3800633bf323684e58c8e117d0a5ea5 /Doc/lib
parent1bff34ab9687129effc2462c0cab7507b0f016e5 (diff)
downloadcpython-git-65faf118b61a14caac332d9f44100502b34b7f98.tar.gz
Fix markup error and minor consistency nit.
Diffstat (limited to 'Doc/lib')
-rw-r--r--Doc/lib/libsys.tex4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/lib/libsys.tex b/Doc/lib/libsys.tex
index ac28e6f975..8d9d022415 100644
--- a/Doc/lib/libsys.tex
+++ b/Doc/lib/libsys.tex
@@ -152,7 +152,7 @@ generally one higher than you might expect, because it includes the
Return the current value of the recursion limit, the maximum depth of
the Python interpreter stack. This limit prevents infinite recursion
from causing an overflow of the C stack and crashing Python. It can
-be set by \function{setrecursionlimit}.
+be set by \function{setrecursionlimit()}.
\end{funcdesc}
\begin{datadesc}{hexversion}
@@ -291,7 +291,7 @@ The highest possible limit is platform-dependent. A user may need to
set the limit higher when she has a program that requires deep
recursion and a platform that supports a higher limit. This should be
done with care, because a too-high limit can lead to a crash.
-\edn{funcdesc}
+\end{funcdesc}
\begin{funcdesc}{settrace}{tracefunc}
Set the system's trace function, which allows you to implement a