[issue10015] Creating a multiprocess.pool.ThreadPool from a child thread blows up.

Terry J. Reedy added the comment: #14881 seems to be a duplicate of this. It was closed in May 2012 after 2.7, 3.2, and 3.3 were patched. The three tests in potential_issue_demo.py now pass with 2.7.5 and 3.3.2. So closing. -- nosy: +terry.reedy resolution: -> duplicate stage: -> com

[issue10015] Creating a multiprocess.pool.ThreadPool from a child thread blows up.

Changes by Richard Oudkerk : -- nosy: +sbt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue10015] Creating a multiprocess.pool.ThreadPool from a child thread blows up.

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue10015] Creating a multiprocess.pool.ThreadPool from a child thread blows up.

Alister Cordiner added the comment: I think that workaround should be: if not hasattr(threading.current_thread(), "_children"): threading.current_thread()._children = weakref.WeakKeyDictionary() -- nosy: +acordiner ___ Python tracker

[issue10015] Creating a multiprocess.pool.ThreadPool from a child thread blows up.

Changes by Vinay Sajip : -- title: Creating a multiproccess.pool.ThreadPool from a child thread blows up. -> Creating a multiprocess.pool.ThreadPool from a child thread blows up. ___ Python tracker ___