traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Revert r61029.

This commit is contained in:
Georg Brandl 2008-02-25 20:20:45 +00:00
parent 976a0590bb
commit fd429063e1
2 changed files with 1 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Doc/library/thread.rst
View File

@ -150,11 +150,6 @@ In addition to these methods, lock objects can also be used via the
exception will be received by an arbitrary thread. (When the :mod:`signal`
module is available, interrupts always go to the main thread.)
* The import machinery is not thread safe. In general, an import may not
have the side effect of importing a module, and only the main thread
should import modules. Imports within or caused by a thread other than
the main thread isn't safe.
* Calling :func:`sys.exit` or raising the :exc:`SystemExit` exception is
equivalent to calling :func:`exit`.
@ -175,3 +170,4 @@ In addition to these methods, lock objects can also be used via the
* When the main thread exits, it does not do any of its usual cleanup (except
that :keyword:`try` ... :keyword:`finally` clauses are honored), and the
standard I/O files are not flushed.

7
Doc/library/threading.rst
View File

@ -562,13 +562,6 @@ the :meth:`setDaemon` method and retrieved with the :meth:`isDaemon` method.
There is a "main thread" object; this corresponds to the initial thread of
control in the Python program. It is not a daemon thread.
.. warning::
The import machinery is not thread safe. In general, an import may not
have the side effect of importing a module, and only the main thread
should import modules. Imports within or caused by a thread other than
the main thread isn't safe.
There is the possibility that "dummy thread objects" are created. These are
thread objects corresponding to "alien threads", which are threads of control
started outside the threading module, such as directly from C code. Dummy