Raymond Hettinger added the comment: FWIW, this isn't even a Python specific behavior. It is just how threads, locks, and processes work (or in this case don't work). The code is doing what it is told to do which happens to not be what you want (i.e. a user bug rather than a Python bug). I think a FAQ entry would be a reasonable place to mention this (it comes up more often than one would hope). ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python resolution: -> not a bug _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue27422> _______________________________________