SCons Hit ‘n Run
Runs SCons, parses its --tree=all output and reruns the build if any of the dependencies change.
Warning: This is a bit of a quick hack. Use at your own peril.
Example
hitnrun -- -j8 will run the command scons --silent --tree=all -j8, rerunning it if any dependencies in the tree change.
Metadata
Release files for hitnrun 0.2
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 |
|---|---|---|---|---|
| hitnrun-0.2.tar.gz | 1.3 kB | Without provenance | Details for hitnrun-0.2.tar.gz |
Release files / hitnrun-0.2.tar.gz
| Download URL | hitnrun-0.2.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
851d0408cb5ead7fc76ce0f5b18d7dd563c8361f7f9eb7d081d589b6522dd9c6
|
|
BLAKE2b-256 checksum How to use checksums |
321281f0527f3c1f25c6d568ea75ce01cbf58e95dfee32d5563fbdd9f305acc3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for hitnrun 0.2
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.