summaryrefslogtreecommitdiffstats
path: root/Doc/api
diff options
context:
space:
mode:
authorSkip Montanaro <skip@pobox.com>2003-07-02 21:38:34 (GMT)
committerSkip Montanaro <skip@pobox.com>2003-07-02 21:38:34 (GMT)
commiteec26f982a6e953eb1d6cc1ca570fb629bdd6ceb (patch)
tree301ae1d6f38a4e16ba7fdaa4949174faf9a2e471 /Doc/api
parent74902508dc395014dbdb9c2ed08263202e5d4e30 (diff)
downloadcpython-eec26f982a6e953eb1d6cc1ca570fb629bdd6ceb.zip
cpython-eec26f982a6e953eb1d6cc1ca570fb629bdd6ceb.tar.gz
cpython-eec26f982a6e953eb1d6cc1ca570fb629bdd6ceb.tar.bz2
Correct documentation of check interval - it's 100 by default, not 10 any
longer. Pointed out by Alex Martelli.
Diffstat (limited to 'Doc/api')
-rw-r--r--Doc/api/init.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/api/init.tex b/Doc/api/init.tex
index 44bfa3e..f7d797c 100644
--- a/Doc/api/init.tex
+++ b/Doc/api/init.tex
@@ -348,7 +348,7 @@ Therefore, the rule exists that only the thread that has acquired the
global interpreter lock may operate on Python objects or call Python/C
API functions. In order to support multi-threaded Python programs,
the interpreter regularly releases and reacquires the lock --- by
-default, every ten bytecode instructions (this can be changed with
+default, every 100 bytecode instructions (this can be changed with
\withsubitem{(in module sys)}{\ttindex{setcheckinterval()}}
\function{sys.setcheckinterval()}). The lock is also released and
reacquired around potentially blocking I/O operations like reading or