Envoy: Python Subprocesses for Humans.
Note: Work in progress.
This is a convenience wrapper around the subprocess module.
You don’t need this.
But you want it.
Usage
Run a command, get the response:
>>> r = envoy.run('git config', data='data to pipe in', timeout=2)
>>> r.status_code
129
>>> r.std_out
'usage: git config [options]'
>>> r.std_err
''
Pipe stuff around too:
>>> r = envoy.run('uptime | pbcopy')
>>> r.command
'pbcopy'
>>> r.status_code
0
>>> r.history
[<Response 'uptime'>]
Metadata
Release files for envoy 0.0.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 |
|---|---|---|---|---|
| envoy-0.0.3.tar.gz | 4.2 kB | Without provenance | Details for envoy-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| envoy-0.0.3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for envoy-0.0.3-py2.py3-none-any.whl |
Total release size: 9.2 kB
Release files / envoy-0.0.3.tar.gz
| Download URL | envoy-0.0.3.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
22b02009cfda2cf2cdb94a75a15ac3fd910aea8685c53e8e03715c7e9d8e8bde
|
|
BLAKE2b-256 checksum How to use checksums |
350155819eb9761339b65be3bda906110a3c7c0e9114374cce12a399c5992fc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / envoy-0.0.3-py2.py3-none-any.whl
| Download URL | envoy-0.0.3-py2.py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
789d274f8bc00401848678c0ee18199c1a57901749ed6b1a03a3ea53ec72ceef
|
|
BLAKE2b-256 checksum How to use checksums |
3671b6ca37dd6bfe6ec851ee385e824fd4e459f2744caa2b8e7533555dcdeb8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for envoy 0.0.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.