> given a remote machine and an SSH connection, just magically make Python code run on that machine, with no hacks involving error-prone shell snippets, tempora

> given a remote machine and an SSH connection, just magically make Python code run on that machine, with no hacks involving error-prone shell snippets, temporary files, or hugely restrictive single use request-response shell pipelines, and suchlike. I wonder if some of this functionality would be easier with a language that inherently supported distributing functions between nodes, e.g. Joe Armstrong's "favorite Erlang Program", the Universal Server: https://joearms.github.io/published/2013-11-21-My-favorite-erlang-program.html https://joearms.github.io/published/2013-11-21-My-favorite-e... I am missing a few of the points, re: * how to bootstrap this onto a system with very limited assumptions about resources/access * performance * market effects of being able to re-use a bunch of existing libraries/scripts/tools written for configuration management or what-have-you in popular python edit - and there's documentation for erlang over ssh: * http://erlang.org/doc/apps/ssh/using_ssh.html http://erlang.org/doc/apps/ssh/using_ssh.html * http://erlang.org/pipermail/erlang-questions/2007-January/024715.html http://erlang.org/pipermail/erlang-questions/2007-January/02... * http://erlang.org/doc/man/slave.html http://erlang.org/doc/man/slave.html