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.

Author chris.jerdonek
Recipients chris.jerdonek, docs@python
Date 2012-07-12.22:00:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1342130435.62.0.0784000861923.issue15339@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2012-07-12 22:00:35chris.jerdoneksetrecipients: + chris.jerdonek, docs@python
2012-07-12 22:00:35chris.jerdoneksetmessageid: <1342130435.62.0.0784000861923.issue15339@psf.upfronthosting.co.za>
2012-07-12 22:00:35chris.jerdoneklinkissue15339 messages
2012-07-12 22:00:34chris.jerdonekcreate