homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: document the threading "facts of life" in Python
Type: behavior Stage: needs patch
Components: Documentation Versions: Python 3.10, Python 3.9
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: chris.jerdonek, docs@python, gregory.p.smith, ncoghlan, pitrou, rhettinger, s7v7nislands@gmail.com, tshepang
Priority: normal Keywords:

Created on 2012年07月12日 22:00 by chris.jerdonek, last changed 2022年04月11日 14:57 by admin.

Messages (5)
msg165336 - (view) Author: Chris Jerdonek (chris.jerdonek) * (Python committer) Date: 2012年07月12日 22:00
I think it would be helpful if the Python documentation included certain high-level information about multi-threading in Python.
At minimum, I think it would help for the documentation to provide a definition that can be linked to of what it means when some part of the Python documentation says something is "thread-safe". In particular, such a definition could clarify that this is different from being atomic. This might best be addressed by an entry in the glossary for the term "thread-safe".
 
Other documentation possibilities include stating what guarantees one should or should not expect regarding thread-safety, both within and across implementations, and providing centralized guidance on how to approach multi-threaded programming in Python. A HOWTO is one possibility for addressing these other possibilities.
This issue stems from the discussion in issue 15329, which is more specific.
msg165338 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2012年07月12日 22:11
This sounds like a good idea. Either a HOWTO or a FAQ would sound appropriate.
msg165397 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2012年07月13日 18:09
If no one gets to it first, I'll write-up a draft when I get a chance.
msg165436 - (view) Author: Alyssa Coghlan (ncoghlan) * (Python committer) Date: 2012年07月14日 07:38
Given the scope of the issue, a concurrent programming howto that lists some of the available options and the caveats associated with each of them seems worthwhile.
msg242046 - (view) Author: Gregory P. Smith (gregory.p.smith) * (Python committer) Date: 2015年04月26日 06:10
This seems somewhat related to the "We need to document Python's concurrency and memory model" that came out at the language summit this year.
History
Date User Action Args
2022年04月11日 14:57:32adminsetgithub: 59544
2020年10月26日 11:48:57iritkatrielsetpriority: low -> normal
stage: needs patch
type: behavior
versions: + Python 3.9, Python 3.10, - Python 2.7, Python 3.2, Python 3.3
2015年04月26日 06:10:53gregory.p.smithsetnosy: + gregory.p.smith
messages: + msg242046
2015年04月25日 15:29:31rhettingersetassignee: rhettinger ->
2015年04月25日 15:09:40s7v7nislands@gmail.comsetnosy: + s7v7nislands@gmail.com
2012年07月14日 07:38:57ncoghlansetnosy: + ncoghlan
messages: + msg165436
2012年07月13日 18:52:34tshepangsetnosy: + tshepang
2012年07月13日 18:09:07rhettingersetpriority: normal -> low

nosy: + rhettinger
messages: + msg165397

assignee: docs@python -> rhettinger
2012年07月12日 22:11:15pitrousetnosy: + pitrou

messages: + msg165338
versions: + Python 2.7, Python 3.2, Python 3.3
2012年07月12日 22:00:35chris.jerdonekcreate

AltStyle によって変換されたページ (->オリジナル) /