Author abn
Recipients abn, docs@python, jnoller, sbt, terry.reedy
Date 2013-02-24.04:24:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361679896.5.0.69308389213.issue17273@psf.upfronthosting.co.za>
In-reply-to
Content
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 pool)."

I am not certain what the best way to phrase this would be, but it would also be helpful to note that this will cause unexpected behavior if a script imports a module that uses a Pool and forks (ie. uses Process() or another Pool()). This is how I bumped into this issue.

Hope this helps.

[1] http://docs.python.org/2/library/multiprocessing.html#using-a-pool-of-workers
[2] http://docs.python.org/3/library/multiprocessing.html#using-a-pool-of-workers
History
Date User Action Args
2013-02-24 04:24:56abnsetrecipients: + abn, terry.reedy, jnoller, docs@python, sbt
2013-02-24 04:24:56abnsetmessageid: <1361679896.5.0.69308389213.issue17273@psf.upfronthosting.co.za>
2013-02-24 04:24:56abnlinkissue17273 messages
2013-02-24 04:24:56abncreate