Infrae extension for Sphinx. This add:
Color scheme for Buildout, because the Ini scheme doesn’t work for multiple line option values.
It defines the code type buildout for the directive code-block.
An directive autointerface to document Zope interfaces.
Example: autointerface:: module.name.to.your.interface.
This create extra documentation if zope.schema fields are encountered on the interface.
An directive autoevent to document Zope events.
Example: autoevent:: module.name.to.your.event.
Changes
1.0 (30/04/2012)
Initial release
Metadata
Release files for sphinxcontrib.infrae 1.0
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 |
|---|---|---|---|---|
| sphinxcontrib.infrae-1.0.tar.gz | 4.4 kB | Without provenance | Details for sphinxcontrib.infrae-1.0.tar.gz |
Release files / sphinxcontrib.infrae-1.0.tar.gz
| Download URL | sphinxcontrib.infrae-1.0.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44b0a678c831b7751a5cd299e8de8913e40f2112274ac5b25e4a33969163dfe2
|
|
BLAKE2b-256 checksum How to use checksums |
98faa54e1226564d2f0886d9f85515f91c44561fb525ef88e80a49c590c83330
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sphinxcontrib.infrae 1.0
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.