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.

Unsupported provider

Author acooke
Recipients acooke
Date 2011-09-05.12:00:44
SpamBayes Score 0.002914267
Marked as misclassified No
Message-id <1315224105.15.0.691135308397.issue12897@psf.upfronthosting.co.za>
In-reply-to
Content
http://stackoverflow.com/questions/7306522/combining-itertools-and-multiprocessing/7307078 suggests (and the idea itself seems reasonable) that it would sometimes be useful for multiprocessing to operate correctly (ie lazily) with lazy input (iterables).  for example, if the input is large, or perhaps generated by some other process "on demand".

obviously this complicates matters, given the asynchronous nature of a worker pool, and would mean re-allocating the results list as required.  but in principle i suspect it would be possible and might be a useful extension.
History
Date User Action Args
2011-09-05 12:01:45acookesetrecipients: + acooke
2011-09-05 12:01:45acookesetmessageid: <1315224105.15.0.691135308397.issue12897@psf.upfronthosting.co.za>
2011-09-05 12:00:45acookelinkissue12897 messages
2011-09-05 12:00:44acookecreate