Add Thread.isActive()

[alanvgreen]

BPO	1107656
Nosy	@birkenfeld
Files	threading-alive-api.diff: patch to threading.py and libthreading.tex

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2007-03-15.21:40:16.000>
created_at = <Date 2005-01-23.05:43:37.000>
labels = ['library']
title = 'Add Thread.isActive()'
updated_at = <Date 2007-03-15.21:40:16.000>
user = 'https://bugs.python.org/alanvgreen'

bugs.python.org fields:

activity = <Date 2007-03-15.21:40:16.000>
actor = 'georg.brandl'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2005-01-23.05:43:37.000>
creator = 'alanvgreen'
dependencies = []
files = ['6450']
hgrepos = []
issue_num = 1107656
keywords = ['patch']
message_count = 3.0
messages = ['47596', '47597', '47598']
nosy_count = 3.0
nosy_names = ['georg.brandl', 'sonderblade', 'alanvgreen']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1107656'
versions = []

[alanvgreen]

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 bpo-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.

[sonderblade]

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.

[birkenfeld]

Superseded by patch bpo-1680968.