a command-line utility to pipe the exit code from a subprocess through one or more modifiers
exit-pipe: a command-line utility to pipe the exit code from a subprocess through one or more modifiers.
This utility executes a specified subprocess, captures its exit code, and exits with the result of piping the exit code through a conditional exit code modifier.
The motivation for this slightly obtuse solution was to work around limitations
imposed by build utilities which execute configurable subprocesses without
exposing full shell access (e.g.
tox) while also maintaining reasonable
portability across multiple operating system environments (thus eliminating the
option of executing an explicit shell within
As of this release, one style of exit code modifier pipeline exists:
bitfield exit code pipeline (activated via the
evaluates the exit code against one or more bitfield masks and either replaces
the exit code with the mapping specified by the first matching bitfield mask or
passes through the unmodified exit code if no bitfield masks match.
This utility has been tested on macOS Catalina 10.15.
Initialize a development environment by executing
will be installed in the
.tox/py38 Python virtual environment binary path.
Remap non-fatal, non-error pylint exit codes to 0
pylint 2.4.3, the utility's exit code is a bitfield that may
be decoded as:
||Fatal message issued|
||Error message issued|
||Warning message issued|
||Refactor message issued|
||Convention message issued|
To remap the exit code for
pylint src such that it exits with:
1for fatal (
1) and error (
2) exit codes, and
0for warning (
4), refactor (
8), convention (
16), and usage (
32) exit codes,
you may pass
exit-pipe as follows:
exit-pipe --bitfield "3:1;60:0" -- pylint src
The equivalent bitfield masks may be specified individually as follows:
exit-pipe --bitfield "1,2:1;4,8,16,32:0" -- pylint src
As niche as this example may be, it serves as a generic workaround to cases
where you may wish to log all
pylint messages while only interpreting a few
classes of messages as build errors. Disabling or ignoring classes of messages
would result in them not being logged.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Hashes for exit_pipe-1.0.0-py3-none-any.whl