This is zzzeek’s own Sphinx layout, used by SQLAlchemy.
This layout is first and foremost pulled in for the SQLAlchemy documentation builds (and possibly other related projects).
Features include:
Uses Mako templates instead of Jinja, for more programmatic capabilities inside of templates.
Layout includes an independently scrollable sidebar
A unique (to Sphinx) “contextual” sidebar contents that shows the current page in context with all sibling pages (like that of MySQL’s docs). This is a form of TOC that Sphinx doesn’t typically have a lot of capability to do (well it could, with some simple feature adds), but IMO this kind of navigation is critical for very large and nested documentation sets, so that the navbar stays relatively small yet provides context as to where you are in the docs and what else is locally available.
Modifications to autodoc which illustrate inherited classes, bases, method documentation illustrates if a method is only inherited from the base or overridden.
A “dynamic base” feature that will, under ReadTheDocs, pull in optional .mako and .py files from the website of your choice that will serve as an alternate base template and a source of extra config setup, respectively, allowing the layout to be integrated into the layout of an external site when viewing on the web.
A “viewsource” extension that can provide highlighted sourcecode to any Python file arbitrarily.
SQLAlchemy-specific stuff, like the [SQL] popups, the dialect info directives.
scss support using pyscss.
Config
in conf.py, the extension is:
extensions = [
'zzzeeksphinx',
]
The theme is:
html_theme = 'zzzeeksphinx'
Other configs that SQLAlchemy has set up; these two are probably needed:
# The short X.Y version. version = "1.0" # The full version, including alpha/beta/rc tags. release = "1.0.0" release_date = "Not released"
Additional configs for the “dynamic site thing” look like:
site_base = os.environ.get("RTD_SITE_BASE", "http://www.sqlalchemy.org")
site_adapter_template = "docs_adapter.mako"
site_adapter_py = "docs_adapter.py"
Configs which do some last-minute translation of module names when running autodoc to display API documentation:
autodocmods_convert_modname = {
"sqlalchemy.sql.sqltypes": "sqlalchemy.types",
"sqlalchemy.sql.type_api": "sqlalchemy.types",
"sqlalchemy.sql.schema": "sqlalchemy.schema",
"sqlalchemy.sql.elements": "sqlalchemy.sql.expression",
"sqlalchemy.sql.selectable": "sqlalchemy.sql.expression",
"sqlalchemy.sql.dml": "sqlalchemy.sql.expression",
"sqlalchemy.sql.ddl": "sqlalchemy.schema",
"sqlalchemy.sql.base": "sqlalchemy.sql.expression"
}
autodocmods_convert_modname_w_class = {
("sqlalchemy.engine.interfaces", "Connectable"): "sqlalchemy.engine",
("sqlalchemy.sql.base", "DialectKWArgs"): "sqlalchemy.sql.base",
}
1 maintainer
Metadata
1 maintainer
Release files for zzzeeksphinx 1.4.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 | |
|---|---|---|---|---|
| zzzeeksphinx-1.4.0.tar.gz | 88.0 kB | Without provenance | Details |
Release files / zzzeeksphinx-1.4.0.tar.gz
| Download URL | zzzeeksphinx-1.4.0.tar.gz |
|---|---|
| Size | 88.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
290faaba3df1143acbd2ca3e1dd99ceab210c08b8860dd2db9435b3f20a7ade7
|
|
BLAKE2b-256 checksum How to use checksums |
7dcc75bd620f3efa6853d111cc01ff4e80abbbba6ca900f5668c8212441e8d28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for zzzeeksphinx 1.4.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.
