Multiprocessing's Pool class __init__ method is written in a way that
makes it very difficult for a subclass to modify self._taskqueue. There
are very good reasons for wanting to do this - ie, making the taskqueue
block when it reaches a certain size. It seems to me that simply moving
the taskqueue assignment into _setup_queues() would do the trick.

The following usenet group discussion contains further details:

http://groups.google.com/group/comp.lang.python/browse_thread/thread/e6c67a09fb20cdec#

I'm not against this; new features will only be committed to the 2.7 and 
3.1.x branches however. 

Something to help speed this up would be an actual patch with docs/tests 
for the module made against python trunk. That way I could review and 
simply submit.

I have attached a patch. All I did was shift the one line from __init__
to _setup_queues.

That's it.

You could take advantage of the change in the following way:

class BlockingPool(pool.Pool):
    def _setup_queues(self):
        pool.Pool._setup_queues(self)
        self._taskqueue = Queue(3)
        self._inqueue = Queue(3)
        self._quick_put = self._inqueue.put

Because of the design of _handle_tasks thread, you need to cap both
_taskqueue and _inqueue for blocking to work out.

I can't see any potential problems caused by this change, but I have
little experience working with this module so far.

Thanks Matthew - I agree, it's simple. But fixing the code is 1/3 of the 
patch. I'll need to add tests/update the ones there as well as modify the 
.rst documentation.

are there really any test/doc changes needed for this?

> are there really any test/doc changes needed for this?

Yes. At bare minimum we need unit tests for the new possible usage of
the API; I'd like docs and an example which show the new usage as
well.

Matthew, would you be willing to write tests + documentation for this?

I should be able to do this in November. For the moment I'm a bit busy.

I would also like to see this functionality as I'm currently using more memory than I'd like when using multiprocessing.Pool

As the name implies, _setup_queues is a private method. It feels a bit weird to recommend overriding it in a subclass.

@swindmill, if you provide a doc/test patch then this can probably be merged.

@pitrou, We could change it to `setup_queues`, though I don't think
even changing the name of "private" methods is a good idea.  It could simply be an alias to `_setup_queues` or vice versa.

It should be possible to do this now through the context, but it's not documented:

>>> import multiprocessing as mp
>>> ctx = mp.get_context()
>>> ctx.SimpleQueue
<bound method BaseContext.SimpleQueue of <multiprocessing.context.SpawnContext object at 0x000001202D30E980>>
>>> ctx.SimpleQueue = list
>>> ctx.SimpleQueue
<class 'list'>