Finally I found you my .. sibling! ;-)

And we looked! Now spotted an email on debian-python@ mailing list.
Meanwhile with @asmacdo we had to come up with a twin brother:

- https://github.com/con/duct

I think one of the main differences is that I am interested not only (or even "not as much") in monitoring rather than in capturing stdout/stderr for those commands. Having those is quite often of paramount importance of figuring out what actually has happened, and thus pairing with https://docs.datalad.org/en/stable/generated/man/datalad-run.html we get a full capture of what was ran, how long it took and resources consumption and what were standard outputs.

Anyways, just wanted to make acquintances. Feel free to ~~burn~~ close upon reading. Or I would be happy to continue dialog etc.

The issue is a discussion rather than an actionable change and names no files, tests, or entry points. Read the linked con/duct project and the linked datalad-run documentation first; the issue does not define a concrete scope or what completion would look like.

Written by the indexing model from the issue text.