3 ms·

It's clear that it "may operate on a local or remote host" and in this case you run a local thread. Just how much is actually implemented is not clear at all. A

by remram 5y ago

It's clear that it "may operate on a local or remote host" and in this case you run a local thread. Just how much is actually implemented is not clear at all. A lot of frameworks are written to be "extensible" but the extensions are left as an exercise to the reader... It is nice to have a self-contained example that you can run on your machine, but I think an example that actually shows the capabilities of the framework will serve you better. E.g. show an example of serving network requests by running services on multiple nodes, rather than a toy function with a toy database. Showing that it's as easy as `run_in_executor()` is nice, but not if it does the exact same thing as `run_in_executor()`.

catern 5y ago
>Showing that it's as easy as `run_in_executor()` is nice, but not if it does the exact same thing as `run_in_executor()`. That's fair and a good point! I suppose reading this, you have no evidence that anything but local_thread exists. I'll change that, somehow, to show that indeed there exist values other than local_thread, and that passing those will run things on remote hosts. This article originally grew out of a tutorial on writing tests using this style, for which running over multiple hosts is not necessary and maybe undesirable... but that's not good for what the article is today.