This package generates a control flow graph of the passed python file based on the AST generated (rather than the bytecode). It supports only a few python statements at this point. Notably absent are exceptions and generators. Essentially, only those constructs found in example.py are supported.
Compatibility
-------------
It was tested on Python 3.6
To run
------
python pycfg/pycfg.py <program to be analyzed> -d
or
python pycfg/pycfg.py <program to be analyzed> -d -y <branch coverage file>
Inspect Makefile for a better idea
1 maintainer
Metadata
1 maintainer
Release files for pycfg 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 | |
|---|---|---|---|---|
| pycfg-0.1.tar.gz | 6.6 kB | Without provenance | Details |
Release files / pycfg-0.1.tar.gz
| Download URL | pycfg-0.1.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
26833dd006dea03040088d7f0da6a3a80350cf4c788c14d50d15d06d2026480f
|
|
BLAKE2b-256 checksum How to use checksums |
1b56e837ca7330163dd5834c0223adf8057513105081b0f7966bed305edac114
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pycfg 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.
