=============

_Pluggable Output Processor_ is an engine to wrap any executabe and capture its output through
a pluggable module to colorize it and/or (re)format.
Features
--------
* easy (to Python programmers ;-) to extend
* 256 color terminal support ;-) configuration files in addition to standard named colors
may contain color definitions as `rgb(r,g,b)` or `gray(n)`
* colorizers for `make`, `cmake`, `gcc` out of the box (more to come ;-)
* some modules are not just a stupid colorizers ;-) For example `gcc` can reformat text for
better readability (really helps to understand template errors). Also `cmake` module can reduce
amount of lines printed during test by collapsing test _intro_ message and _result_ into a single one.
Installation
------------
Easy!
$ pip install outproc
For Gentoo users there is a [live ebuild][raw-ebuild] in my [repository][my-overlay].
Also (for Gentoo users again ;-) `eselect` module from `contrib/` will be installed by the ebuild.
Users of other distros have to make symlinks to required modules manually (replace `<install-prefix>`
with your actual path):
$ ln -s <install-prefix>/bin/outproc /usr/lib/outproc/bin/<module-name>
and then make sure `/usr/lib/outproc/bin` placed __before__ `/usr/bin` (and anything else) in your
user/system `PATH` environment. The path `/usr/lib/outproc/bin` is just an example. You can choose
whatever you like instead (e.g. `/home/<login>/.local/bin/` for user based install layout).
List of available modules (plugins) can be obtained from command:
$ outproc -l
List of available modules:
c++
cc
cmake
diff
g++
gcc
make
mount
For example, to install the `make` module do the following:
$ ln -s <install-prefix>/bin/outproc /usr/lib/outproc/bin/make
Then you may edit `/etc/outproc/make.conf` to adjust color settings. Note that `gcc`, `g++`, `cc` and `c++`
are the same module actually (named after typical GCC executables) and use the same `/etc/outproc/gcc.conf`
config file.
[raw-ebuild]: https://github.com/zaufi/zaufi-overlay/blob/master/dev-util/pluggable-output-processor/pluggable-output-processor-scm.ebuild
[my-overlay]: https://github.com/zaufi/zaufi-overlay/ "My ebuilds overlay"
Metadata
Release files for outproc 0.20
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| outproc-0.20.tar.gz | 48.9 kB | Without provenance | Details for outproc-0.20.tar.gz |
Release files / outproc-0.20.tar.gz
| Download URL | outproc-0.20.tar.gz |
|---|---|
| Size | 48.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a3578049549eb06b543d1f8fb189d257c653d276271bedc64483b8cf606b4eb8
|
|
BLAKE2b-256 checksum How to use checksums |
d3020309b0c0d9ea806d96a0a50831ff26eb27e7f3b22029cda37ea2ad4a737a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for outproc 0.20
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.