RemoteTox
Remote testing of python environments (that use tox).
What this does
Acquires a lock to ensure simultaneous repositories are not being tested.
Connects to (randomly selected if multiple are given) remote machine (ssh keys need to be setup to allow this to happen in a non-intrusive way).
Archives the current working directory into a tarball.
Sends this tarball to the remote machine (after removing any old or previous tarballs, test environments…).
Runs tox on the remote machine, proxying the stderr/stdout to the local stderr/stdout (making it look like the output of that remote program is actually local).
Returns the remote tox programs exit code as the local programs exit code (making it look like the remote programs exit code was the local programs exit code).
1 maintainer
Metadata
1 maintainer
Release files for remote_tox 0.0.1
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 |
|---|---|---|---|---|
| remote_tox-0.0.1.tar.gz | 8.7 kB | Without provenance | Details for remote_tox-0.0.1.tar.gz |
Release files / remote_tox-0.0.1.tar.gz
| Download URL | remote_tox-0.0.1.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c96ea434a133ddd8722438e38c304830863ac260862eba1b87db2b575bc0767
|
|
BLAKE2b-256 checksum How to use checksums |
3407266cd31954e288822539260f1591e0198198903c5a985ecf0822862dee82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for remote_tox 0.0.1
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.
