Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
8784bae6
Commit
8784bae6
authored
Mar 15, 2007
by
Georg Brandl
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Patch #1680978: consistently use "alive" instead of "active" in the
thread lib doc.
parent
72d9eec1
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
20 additions
and
24 deletions
+20
-24
Doc/lib/libthreading.tex
Doc/lib/libthreading.tex
+20
-24
No files found.
Doc/lib/libthreading.tex
View file @
8784bae6
...
...
@@ -15,10 +15,9 @@ situations where \module{threading} cannot be used because
This module defines the following functions and objects:
\begin{funcdesc}
{
activeCount
}{}
Return the number of
currently active
\class
{
Thread
}
objects.
The
returned count is equal to the length of the list returned by
Return the number of
\class
{
Thread
}
objects currently alive. The
returned count is equal to the length of the list returned by
\function
{
enumerate()
}
.
A function that returns the number of currently active threads.
\end{funcdesc}
\begin{funcdesc}
{
Condition
}{}
...
...
@@ -36,10 +35,10 @@ is returned.
\end{funcdesc}
\begin{funcdesc}
{
enumerate
}{}
Return a list of all
currently active
\class
{
Thread
}
objects.
The list includes daemonic threads, dummy thread objects created
by
\function
{
currentThread()
}
, and the main thread. It excludes terminated
threads and threads that have not yet been started.
Return a list of all
\class
{
Thread
}
objects currently alive. The list
includes daemonic threads, dummy thread objects created by
\function
{
currentThread()
}
, and the main thread. It excludes
t
erminated t
hreads and threads that have not yet been started.
\end{funcdesc}
\begin{funcdesc}
{
Event
}{}
...
...
@@ -526,12 +525,9 @@ calling the thread's \method{start()} method. This invokes the
\method
{
run()
}
method in a separate thread of control.
Once the thread's activity is started, the thread is considered
'alive' and 'active' (these concepts are almost, but not quite
exactly, the same; their definition is intentionally somewhat
vague). It stops being alive and active when its
\method
{
run()
}
method terminates -- either normally, or by raising an unhandled
exception. The
\method
{
isAlive()
}
method tests whether the thread is
alive.
'alive'. It stops being alive when its
\method
{
run()
}
method terminates
-- either normally, or by raising an unhandled exception. The
\method
{
isAlive()
}
method tests whether the thread is alive.
Other threads can call a thread's
\method
{
join()
}
method. This blocks
the calling thread until the thread whose
\method
{
join()
}
method is
...
...
@@ -551,14 +547,13 @@ There is a ``main thread'' object; this corresponds to the
initial thread of control in the Python program. It is not a
daemon thread.
There is the possibility that ``dummy thread objects'' are
created. These are thread objects corresponding to ``alien
threads''. These are threads of control started outside the
threading module, such as directly from C code. Dummy thread objects
have limited functionality; they are always considered alive,
active, and daemonic, and cannot be
\method
{
join()
}
ed. They are never
deleted, since it is impossible to detect the termination of alien
threads.
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 thread objects have limited
functionality; they are always considered alive and daemonic, and
cannot be
\method
{
join()
}
ed. They are never deleted, since it is
impossible to detect the termination of alien threads.
\begin{classdesc}
{
Thread
}{
group=None, target=None, name=None,
...
...
@@ -646,7 +641,8 @@ name. The initial name is set by the constructor.
Return whether the thread is alive.
Roughly, a thread is alive from the moment the
\method
{
start()
}
method
returns until its
\method
{
run()
}
method terminates.
returns until its
\method
{
run()
}
method terminates. The module
function
\function
{
enumerate()
}
returns a list of all alive threads.
\end{methoddesc}
\begin{methoddesc}
{
isDaemon
}{}
...
...
@@ -659,8 +655,8 @@ This must be called before \method{start()} is called.
The initial value is inherited from the creating thread.
The entire Python program exits when no a
ctive non-daemon
threads are
left.
The entire Python program exits when no a
live non-daemon threads are
left.
\end{methoddesc}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment