[Patches] [ python-Patches-1107656 ] Add Thread.isActive()

[SourceForge.net]

Patches item #1107656, was opened at 2005-01-23 05:43
Message generated for change (Comment added) made by gbrandl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1107656&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Library (Lib)
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 5
Private: No
Submitted By: Alan Green (alanvgreen)
Assigned to: Nobody/Anonymous (nobody)
Summary: Add Thread.isActive()

Initial Comment:
The documentation for threading.Thread states: 

"""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 run() method terminates
- either normally, or by raising an unhandled exception."""

This is confusing. There doesn't seem to be a need to
expose both 'alive' and 'active' concepts in the API. 

The confusion was reported as part of Issue 912943
"7.5.6 Thread Objects is too vague"

This patch:
- adds an isActive() method to Thread, that tests
whether the thread is active. 
- adds documentation for isActive()
- modifies the documentation for isAlive(), noting that
it is deprecated and explaining why.


----------------------------------------------------------------------

>Comment By: Georg Brandl (gbrandl)
Date: 2007-03-15 21:40

Message:
Logged In: YES 
user_id=849994
Originator: NO

Superseded by patch #1680968.

----------------------------------------------------------------------

Comment By: Björn Lindqvist (sonderblade)
Date: 2005-05-09 00:02

Message:
Logged In: YES 
user_id=51702

I'm confused. Wouldn't it be better to just keep the
isAlive() method instead of deprecating it and introducing
isActive() in its place? In that way you only have to change
the documentation and the API can remain intact.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1107656&group_id=5470