qubic.sphinx.graphvizinclude
Overview
This package defines an extension for the Sphinx documentation system. The extension allows generation of Graphviz from external .dot resources
Installation
Install via easy_install:
$ bin/easy_install qubic.sphinx.graphvizinclude
or any other means which gets the package on your PYTHONPATH.
Registering the Extension
Add qubic.sphinx.graphvizinclude to the extensions list in the conf.py of the Sphinx documentation for your product. E.g.:
extensions = ['sphinx.ext.autodoc',
'sphinx.ext.doctest',
'qubic.sphinx.graphvizinclude',
]
Using the Extension
At appropriate points in your document, call out the interface autodocs via:
.. graphvizinclude:: ./path_to/graph_definition.dot
change history
0.1
first release
Metadata
Release files for qubic.sphinx.graphvizinclude 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 |
|---|---|---|---|---|
| qubic.sphinx.graphvizinclude-0.1.tar.gz | 6.8 kB | Without provenance | Details for qubic.sphinx.graphvizinclude-0.1.tar.gz |
Release files / qubic.sphinx.graphvizinclude-0.1.tar.gz
| Download URL | qubic.sphinx.graphvizinclude-0.1.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
61df0fa5373dd02d8911e04de02699802e97e8790fc0b78f048272a0e2992a3d
|
|
BLAKE2b-256 checksum How to use checksums |
c5ed175d43784ca6c58c61190e05ddb2a8026a6db1cf0ccb7738b8b5f74637b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for qubic.sphinx.graphvizinclude 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.