MartinPdeS-docs
Shared Sphinx defaults for the MartinPdeS scientific Python repositories.
The package intentionally uses a flat layout. A project keeps its own documentation content and assets, while this package supplies common Sphinx extensions, theme defaults, responsive layout settings, and gallery behavior. It also provides the shared author metadata, autodoc defaults, document defaults, theme navigation, repository links, version switcher, and output metadata used across the package family.
In a project's docs/source/conf.py:
from martinpdes_docs import configure
globals().update(
configure(
project="PackLab",
package="PackLab",
repository="MartinPdeS/PackLab",
logo="_static/logo.png",
favicon="_static/favicon.png",
)
)
Project-specific values can be assigned below this call to override any shared default.
For a multi-section Sphinx-Gallery, pass the section names instead of repeating the directory mappings:
globals().update(
configure(
project="FlowCyPy",
package="FlowCyPy",
repository="MartinPdeS/FlowCyPy",
gallery_sections=["tutorials", "studies", "validation"],
gallery_default_thumb="_static/gallery-default.png",
)
)
Use gallery_options for project-specific Sphinx-Gallery settings such as an
additional image scraper or an example error policy.
For packages with compiled extensions, set prefer_installed_package=True so
documentation builds import the installed wheel instead of the source
checkout.
The shared configuration also owns the common dark-mode context, CSS files,
autodoc defaults, and navigation metadata. Add only project-specific values in
conf.py, for example:
globals().update(
configure(
project="SuPyMode",
package="SuPyMode",
repository="MartinPdeS/SuPyMode",
extension_additions=["pyvista.ext.plot_directive"],
html_css_files=["layout.css"],
autodoc_default_options={"members": True},
logo_text="",
)
)
Use include_gallery=False for documentation sites without executable
examples. The default theme, context, CSS, and extension set then remain
centralized in this package.
Metadata
Release files for MartinPdeS-docs 0.2.3
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 | |
|---|---|---|---|---|
| martinpdes_docs-0.2.3.tar.gz | 6.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| martinpdes_docs-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.0 kB
Release files / martinpdes_docs-0.2.3.tar.gz
| Download URL | martinpdes_docs-0.2.3.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a005e64ccb17a101024e89cdd8ed65ed0f91fbc7114138c46a1540f2bf8aebf3
|
|
BLAKE2b-256 checksum How to use checksums |
9c9ce01fb50761b80b69bf3cc37b0d745242d3da9a11162fef1faf9c4092ddf6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / martinpdes_docs-0.2.3-py3-none-any.whl
| Download URL | martinpdes_docs-0.2.3-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f8a1db37e93a14f63f4b305b962a99114ae0eb84e57671105d627b4b0efddd8
|
|
BLAKE2b-256 checksum How to use checksums |
fbd1338e2b79b591155e7ad7bc2d40cd271a5662e047f913da878784b7e897b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for MartinPdeS-docs 0.2.3
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.