Interface for controlling program execution:
Example:
from execcontrol import ControlledExec ce = ControlledExec(“./a.out”) ce.set_break(“main”) ce.exec_run() print ce.get_variables() ce.next() print ce.get_variables()
1 maintainer
Metadata
1 maintainer
Release files for pyexeccontrol 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 | |
|---|---|---|---|---|
| pyexeccontrol-0.0.3.tar.gz | 2.4 kB | Without provenance | Details |
Release files / pyexeccontrol-0.0.3.tar.gz
| Download URL | pyexeccontrol-0.0.3.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fba274dc2079f064314722a60d017e823c835c1569d868780876a7ad503914a7
|
|
BLAKE2b-256 checksum How to use checksums |
5313703fc7aed6466f38c3857c31d9cb0e9a4ee9dd91c8e5fe9c4195b729d9b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyexeccontrol 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.
