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 maggyero
Recipients asvetlov, bquinlan, lukasz.langa, maggyero, methane, ned.deily, pitrou, serhiy.storchaka
Date 2019-06-15.22:21:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560637275.58.0.89059030021.issue37294@roundup.psfhosted.org>
In-reply-to
Content
And like the `concurrent.futures` module for `concurrent.futures.ProcessPoolExecutor` but not for `concurrent.futures.ThreadPoolExecutor` (see above), the `multiprocessing.pool` module seems also affected by a similar problem for `multiprocessing.pool.Pool` (process pools) but not for `multiprocessing.pool.ThreadPool` (thread pools).

Indeed the following code:

    import multiprocessing.pool
    
    class A:
        def f(self):
            print("called")
    
    class B(A):
        def f(self):
            pool = multiprocessing.pool.Pool(2)
            pool.apply(super().f)
    
    if __name__ == "__main__":
        B().f()

raises the following exception:

> AssertionError: daemonic processes are not allowed to have children
History
Date User Action Args
2019-06-15 22:21:15maggyerosetrecipients: + maggyero, bquinlan, pitrou, ned.deily, asvetlov, methane, lukasz.langa, serhiy.storchaka
2019-06-15 22:21:15maggyerosetmessageid: <1560637275.58.0.89059030021.issue37294@roundup.psfhosted.org>
2019-06-15 22:21:15maggyerolinkissue37294 messages
2019-06-15 22:21:15maggyerocreate