Sphinx-Needs can be fully configured via conf.py, but can also load configuration from a ubproject.toml file. This file can be created and updated automatically via the needs-config-writer Sphinx extension.
Many Sphinx projects want to generate a part of the Sphinx-Needs configuration automatically. Tools like ubCode / ubc require a declarative format to ingest configuration. This extension tries to bridge the gap between Sphinx’s dynamic Python configuration and the need for a static configuration file.
Complete documentation: https://needs-config-writer.useblocks.com
Metadata
Release files for needs-config-writer 0.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| needs_config_writer-0.2.4.tar.gz | 11.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| needs_config_writer-0.2.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.8 kB
Release files / needs_config_writer-0.2.4.tar.gz
| Download URL | needs_config_writer-0.2.4.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c89375848c822e891b3cca48783f3cc3f7cbd3c02cba19418de146ca077f212
|
|
BLAKE2b-256 checksum How to use checksums |
c50eedfe8fa008ce27a12b0848a2982f70d5213420c73298e48e4a0e1e4613e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2025.
Transparency logRelease files / needs_config_writer-0.2.4-py3-none-any.whl
| Download URL | needs_config_writer-0.2.4-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f0702574081bb8ed7d896aadfb73c0e48af099dc0d4227cc2bac957ed8ea4f6
|
|
BLAKE2b-256 checksum How to use checksums |
24a19f1fc6c25eaed7379834417a977606750eea71ab4c53ac1361e37f7099ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2025.
Transparency log