Skip to main content

Importable CLI-passthrough with bells and whistles.

Project description

README

This project provides an entry point cli-passthrough in the terminal that accepts any amount of parameters, and runs those parameters as it's own command. Except in a few special cases, this will output to the terminal exactly what the command would have, including any formatting done with escape sequences. Both the combined stdout and stderr are logged, with order preserved, in logs/history.log, and the stderr by itself is logged in /logs/stderr.log. These log files are written to in realtime. The output to the terminal is also in realtime.

This project was motivated by making a wrapper on another application which needed to be used over the CLI. I wanted to also use the wrapper from the CLI as well. I wanted to see the output of the program I was invoking in real-time, in the same formatting, and log everything. In other words, I wanted the following:

  1. ANY COMMAND: Run nearly any command given to it.
  2. FLEXIBLE LOGGING: Capture stdout and stderr independently for flexible logging.
  3. ORDER PESERVATION: Preserve order of stdout and stderr
  4. REALTIME OUTPUT: Output to the screen in realtime, i.e. don't wait for the command to exit before dumping to the screen.
  5. EXIT STATUS: Capture exit code
  6. FORMATTING PRESERVED: Preserve ANSI escape sequences so most things are still formatted as if not run through this passthrough.
  7. INTERACTIVE, i.e. allow prompting for input.
1 2 3 4 5 6 7 note
os.system Y N Y Y Y Y Y Doesn't capture output at all
os.popen N N Y N N Y N Deprecated & obsolete
os.exec* Y N - N N N N Really not the intended use
pexpect Y N Y Y Y Y Y Bad logging
subprocess.popen + threads Y Y Y N Y Y/N N Threads just enable separate logging, not realtime output
subprocess.popen + pty Y Y Y Y Y Y Y We got it!

Known Limitations

This implementation of subprocess.popen + pty currently has the following limitations:

  1. It doesn't run every command, just most. ssh doesn't work :/

  2. It makes assumptions about the terminal size. It would be better if it detected the terminal the python is ran in, and use the same dimensions.

This is very much largely adapted (copied) from this SO post. I just wrapped it up into an importable function, gave it a CLI itself, and made basic logging to illustrate the point. Feel free to copy/paste/tweek it yourself.

If you find something better please let me know! I'd be more than happy to upgrade or replace this. This is simply the best I've found so far.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

CLI_passthrough-0.1.1-py3-none-any.whl (5.3 kB view details)

Uploaded Python 3

File details

Details for the file CLI_passthrough-0.1.1-py3-none-any.whl.

File metadata

File hashes

Hashes for CLI_passthrough-0.1.1-py3-none-any.whl
Algorithm Hash digest
SHA256 5c2ba6bcd70921068246c90bfb4c591070b1d0b919fc0cc6610271e0dc290ad2
MD5 3763a9032086bbea90d740344bbcd90d
BLAKE2b-256 bec2d7b80c4a7d417b9ff441ff7fad6e5014fec3e690d8de1d287d6416a5d3df

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page