no.email at nospam.invalid
Wed Aug 11 23:38:50 CEST 2010
EW <ericwoodworth at gmail.com> writes:
> Well I can't really explain it but 1 Queue per task for what I'm
> designing just doesn't feel right to me. It feels like it will lack
> future flexibility.
That makes no sense at all. Multiple readers and writers per queue are
the way Python queues are designed to work. The normal way to spray a
bunch of concurrent tasks to worker threads is just have a bunch of
workers listening to one queue. It's the same way at the producer end.
More information about the Python-list