This package contains a fork of the zopeext Sphinx extension.
Original documentation: http://packages.python.org/sphinxcontrib-zopeext
Install with pip install j1m.sphinxautointerface.
To use this extension, include ‘j1m.sphinxautointerface’ in your extensions list in the conf.py file for your documentation.
This provides some support for Zope interfaces by providing an autointerface directive that acts like autoclass except uses the Zope interface methods for attribute and method lookup (the interface mechanism hides the attributes and method so the usual autoclass directive fails.) Interfaces are intended to be very different beasts than regular python classes, and as a result require customized access to documentation, signatures etc.
See Also
1 maintainer
Metadata
1 maintainer
Release files for j1m.sphinxautointerface 0.3.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 |
|---|---|---|---|---|
| j1m.sphinxautointerface-0.3.0.tar.gz | 4.5 kB | Without provenance | Details for j1m.sphinxautointerface-0.3.0.tar.gz |
Release files / j1m.sphinxautointerface-0.3.0.tar.gz
| Download URL | j1m.sphinxautointerface-0.3.0.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
633d9f3a3eea96b559e43fd138c1408ff64a82481ccbf859cb616c614ad4b9dc
|
|
BLAKE2b-256 checksum How to use checksums |
38822464695c28112f8722ffec7e8a06e86a57bbb1cfb5e7ff9642b98f784a03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for j1m.sphinxautointerface 0.3.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.
