Mike DePalatis

Thanks for the clarification. I think I was a bit confused since the frontend has to poll for results, but what you're describing makes a lot of sense. The tricky...

Yes, that would be the idea.

That's a good point. I like the approach of adding an additional command for running the poller, though I'm not sure offhand what the best way to implement that would...

Try upgrading to Tornado 6.0.4 which was released this week. It [fixed](https://www.tornadoweb.org/en/stable/releases/v6.0.4.html#bug-fixes) some `StreamClosedError` bug. I'm not sure if that's what you're experiencing or not, but it's worth a quick...

This would definitely be helpful. I'm especially interested in the information here given that the HTCondor testing is currently... limited and would be interested in helping to improve that.

@lesteve, thanks for the pointers! I'll see if I can find some time in the coming days to work on this.

For what it's worth, this should be pretty trivial to make async using `asyncio.create_subprocess_exec`. Its API is nearly identical to using `subprocess.Popen`.

Or to not have to change anything else using the `_call` method with something like: ```python async def _submit_job(self, script_filename): return await asyncio.get_running_loop().run_in_executor(None, self._call(...)) ```

> If something is required by most users then it should have a sensible default, as we do today. I think there are two issues here: 1. One person's sensible...

Great talk, @jeffbass! Just one comment on what you said about mulitprocessing: > But multiprocessing has its own drawbacks: Python objects cannot be shared directly between processes and multiprocessing.queue()'s between...