On Fri, Feb 19, 2016 at 10:18 AM, Joseph L. Casale
wrote:
>> It's still not clear to me specifically what you're trying to do. It
>> would really help if you would describe the problem in more detail.
>> Here's what I think you're trying to do:
>>
>> 1) Submit a task to a ThreadPoolExecutor and ge
> It's still not clear to me specifically what you're trying to do. It
> would really help if you would describe the problem in more detail.
> Here's what I think you're trying to do:
>
> 1) Submit a task to a ThreadPoolExecutor and get back a future.
>
> 2) When the task is complete, submit anot
On Thu, Feb 18, 2016 at 12:06 PM, Joseph L. Casale
wrote:
> On Thur, Feb 17, 2016 at 9:24 AM, Ian Kelly wrote:
>>> What is the pattern for chaining execution of tasks with ThreadPoolExecutor?
>>> Callbacks is not an adequate facility as each task I have will generate new
>>> output.
>>
>> Can yo
On Thur, Feb 17, 2016 at 9:24 AM, Ian Kelly wrote:
>> What is the pattern for chaining execution of tasks with ThreadPoolExecutor?
>> Callbacks is not an adequate facility as each task I have will generate new
>> output.
>
> Can you specify in more detail what your use case is?
>
> If you don't m
On Tue, Feb 16, 2016 at 2:48 PM, Joseph L. Casale
wrote:
> What is the pattern for chaining execution of tasks with ThreadPoolExecutor?
> Callbacks is not an adequate facility as each task I have will generate new
> output.
Can you specify in more detail what your use case is?
If you don't mind
