classification
Title: document the threading "facts of life" in Python
Type: Stage:
Components: Documentation Versions: Python 3.3, Python 3.2, Python 2.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: rhettinger Nosy List: chris.jerdonek, docs@python, ncoghlan, pitrou, rhettinger, tshepang
Priority: low Keywords:

Created on 2012-07-12 22:00 by chris.jerdonek, last changed 2012-07-14 07:38 by ncoghlan.

Messages (4)
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: Nick 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.
History
Date User Action Args
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