summaryrefslogtreecommitdiff
path: root/Doc/lib/libthread.tex
diff options
context:
space:
mode:
authorTim Peters <tim.peters@gmail.com>2006-06-04 23:52:47 +0000
committerTim Peters <tim.peters@gmail.com>2006-06-04 23:52:47 +0000
commit28eeefe566d77cd3af3d675c4f2216c5033fe538 (patch)
tree7fec63fcf38c5dbe611860fb74e8c49206d2e581 /Doc/lib/libthread.tex
parentc7d14452a4ed303d38498cc16c3cfc0beed9b843 (diff)
downloadcpython-git-28eeefe566d77cd3af3d675c4f2216c5033fe538.tar.gz
Revert revisions:
46640 Patch #1454481: Make thread stack size runtime tunable. 46647 Markup fix The first is causing many buildbots to fail test runs, and there are multiple causes with seemingly no immediate prospects for repairing them. See python-dev discussion. Note that a branch can (and should) be created for resolving these problems, like svn copy svn+ssh://svn.python.org/python/trunk -r46640 svn+ssh://svn.python.org/python/branches/NEW_BRANCH followed by merging rev 46647 to the new branch.
Diffstat (limited to 'Doc/lib/libthread.tex')
-rw-r--r--Doc/lib/libthread.tex19
1 files changed, 0 insertions, 19 deletions
diff --git a/Doc/lib/libthread.tex b/Doc/lib/libthread.tex
index 82b04f4a42..9573ab3fb0 100644
--- a/Doc/lib/libthread.tex
+++ b/Doc/lib/libthread.tex
@@ -74,25 +74,6 @@ data. Thread identifiers may be recycled when a thread exits and
another thread is created.
\end{funcdesc}
-\begin{funcdesc}{stack_size}{\optional{size}}
-Return the thread stack size used when creating new threads. The
-optional \var{size} argument specifies the stack size to be used for
-subsequently created threads, and must be 0 (use platform or
-configured default) or a positive integer value of at least 32,768 (32kB).
-If changing the thread stack size is unsupported, or the specified size
-is invalid, a \exception{RuntimeWarning} is issued and the stack size is
-unmodified. 32kB is currently the minimum supported stack size value,
-to guarantee sufficient stack space for the interpreter itself.
-Note that some platforms may have particular restrictions on values for
-the stack size, such as requiring allocation in multiples of the system
-memory page size - platform documentation should be referred to for more
-information (4kB pages are common; using multiples of 4096 for the
-stack size is the suggested approach in the absence of more specific
-information).
-Availability: Windows, systems with \POSIX{} threads.
-\versionadded{2.5}
-\end{funcdesc}
-
Lock objects have the following methods: