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 rhettinger
Recipients docs@python, rhettinger, vstinner
Date 2018-11-19.22:13:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
One idea is that you could author a threading HOWTO document that covers atomicity, locks, queues, reentrancy, etc.  This is a thorny topic and it would be nice to have the principles and techniques collected in one place.

Ideally, it would include examples of what to expect in various situations.  For example, the pure python OrderedDict can be put in an inconsistent state if two threads make updates without a mutex; however, the containers implemented in C can never be broken even if they don't guarantee atomicity (i.e. a dict update making a pure python callback to __hash__ will never result in a broken dict).

ISTM that the docs have presumed that people using threading know what they're doing; however, we know that isn't always true ;-)
Date User Action Args
2018-11-19 22:13:05rhettingersetrecipients: + rhettinger, vstinner, docs@python
2018-11-19 22:13:05rhettingersetmessageid: <>
2018-11-19 22:13:05rhettingerlinkissue35276 messages
2018-11-19 22:13:05rhettingercreate