[issue17273] multiprocessing.pool.Pool task/worker handlers are not fork safe

2013-07-02 Thread Roundup Robot
Roundup Robot added the comment: New changeset 389788ba6bcb by Richard Oudkerk in branch '2.7': Issue #17273: Clarify that pool methods can only be used by parent process. http://hg.python.org/cpython/rev/389788ba6bcb New changeset 57fe80fda9be by Richard Oudkerk in branch '3.3': Issue #17273: C

[issue17273] multiprocessing.pool.Pool task/worker handlers are not fork safe

2013-02-23 Thread Arun Babu Neelicattu
Arun Babu Neelicattu added the comment: Terry, I think the best place to make a note of this would be at [1,2]. As for what should be noted, something along the lines of what Richard mentioned should suffice. "A pool should only be used by the process that created it (unless you use a managed

[issue17273] multiprocessing.pool.Pool task/worker handlers are not fork safe

2013-02-22 Thread Terry J. Reedy
Terry J. Reedy added the comment: Arun, can you suggest a sentence to add and where to add it? -- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python ___ Python tracker __

[issue17273] multiprocessing.pool.Pool task/worker handlers are not fork safe

2013-02-22 Thread Richard Oudkerk
Richard Oudkerk added the comment: > Richard, are you suggesting that we close this, or do you see an > actionable issue? (a plausible patch to the repository?) I skimmed the documentation and could not see that this restriction has been documented. So I think a documentation patch would be a

[issue17273] multiprocessing.pool.Pool task/worker handlers are not fork safe

2013-02-22 Thread Terry J. Reedy
Terry J. Reedy added the comment: Arun, to call this a bug, you need to demonstrate a conflict between behavior and doc, and I do not see that you have. Richard, are you suggesting that we close this, or do you see an actionable issue? (a plausible patch to the repository?) -- nosy: +

[issue17273] multiprocessing.pool.Pool task/worker handlers are not fork safe

2013-02-22 Thread Richard Oudkerk
Richard Oudkerk added the comment: A pool should only be used by the process that created it (unless you use a managed pool). If you are creating long lived processes then you could create a new pool on demand. For example (untested) pool_pid = (None, None) def get_pool(): g

[issue17273] multiprocessing.pool.Pool task/worker handlers are not fork safe

2013-02-21 Thread Arun Babu Neelicattu
Arun Babu Neelicattu added the comment: I should have mentioned this too, [GOOD] Workaround: Probably the 'correct' way to achieve what is required in the example, could be to use a managed pool. pool = multiprocessing.Manager().Pool() -- ___ Pytho

[issue17273] multiprocessing.pool.Pool task/worker handlers are not fork safe

2013-02-21 Thread Arun Babu Neelicattu
Changes by Arun Babu Neelicattu : -- nosy: +jnoller, sbt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue17273] multiprocessing.pool.Pool task/worker handlers are not fork safe

2013-02-21 Thread Arun Babu Neelicattu
New submission from Arun Babu Neelicattu: The task/worker handler threads in the multiprocessing.pool.Pool class are (in accordance to posix standards) not copied over when the process containing the pool is forked. This leads to a situation where the Pool keeps receiving tasks but the tasks