|
|
|
|
@ -31,6 +31,8 @@ LAN feel like I were configuring a host on Mars. Poking through what Ansible
|
|
|
|
|
was doing, I was shocked to discover it writing temporary files everywhere, and
|
|
|
|
|
uploading a 56KiB zip file apparently for every playbook step.
|
|
|
|
|
|
|
|
|
|
.. image:: _static/wtf.gif
|
|
|
|
|
|
|
|
|
|
Searching around for something to play with, I came across my forgotten
|
|
|
|
|
``src/econtext`` directory and somehow in a few hours managed to squash most of
|
|
|
|
|
the race conditions and logic bugs that were preventing reliable operation,
|
|
|
|
|
@ -39,7 +41,11 @@ write the IO and log forwarders, rewrite the module importer, move from
|
|
|
|
|
special cases out of the main loop.
|
|
|
|
|
|
|
|
|
|
So there you have it. As of writing :py:mod:`econtext.core` consists of 550
|
|
|
|
|
source lines, and those 550 lines have taken me almost a decade to write.
|
|
|
|
|
source lines, and those 550 lines have taken me almost a decade to write. I
|
|
|
|
|
have long had a preference for avoiding infrastructure work commercially, not
|
|
|
|
|
least for the inescapable depression induced by considering the wasted effort
|
|
|
|
|
across the world caused by universally horrific tooling. This is my tiny
|
|
|
|
|
contribution to the solution, I hope you find it useful.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Future
|
|
|
|
|
@ -47,6 +53,7 @@ Future
|
|
|
|
|
|
|
|
|
|
* Connect back using TCP and SSL.
|
|
|
|
|
* Python 3 support.
|
|
|
|
|
* Windows support via psexec or similar.
|
|
|
|
|
* Predictive import: reduce roundtrips by pipelining modules observed to
|
|
|
|
|
probably be requested in future.
|
|
|
|
|
* Provide a means for waiting on multiple
|
|
|
|
|
|