pipeline functionality.
This package leverages subprocess to provide easy-to-use cross-platform command
pipelines with a Posix flavour: you can have chains of commands using ;, &,
pipes using | and |&, and redirection.
The latest version of sarge can be found `here <https://bitbucket.org/vinay.sajip/sarge/>`_::
https://bitbucket.org/vinay.sajip/sarge/
The latest documentation (kept updated between releases) is `here <http://sarge.readthedocs.org/>`_::
http://sarge.readthedocs.org/
Please report any problems or suggestions for improvement either via the
`mailing list <http://groups.google.com/group/python-sarge/>`_ or the `issue
tracker <https://bitbucket.org/vinay.sajip/sarge/issues/new>`_.
Metadata
Release files for sarge 0.1.3
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 |
|---|---|---|---|---|
| sarge-0.1.3.tar.gz | 49.6 kB | Without provenance | Details for sarge-0.1.3.tar.gz |
Release files / sarge-0.1.3.tar.gz
| Download URL | sarge-0.1.3.tar.gz |
|---|---|
| Size | 49.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c929be34d0a242f15e063d91f0ce0af8679b2fab0c92712ff21acd2372447338
|
|
BLAKE2b-256 checksum How to use checksums |
7783c6c2c94e5874539716af5803c6f81a24be8911ffac97c1580c11dac55883
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sarge 0.1.3
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.