Minimal working example of a packaged Python project. Key integrations include:
- Build System (Poetry).
- Test Framework (PyTest).
- Auto-docs with Markdown and ReST support (pdoc).
- CI/CD (GitHub Actions).
Contents
Structure
Documentation is generated from Python docstrings and takes a structure mirroring that of the source code (API documentation).
Initial focus could be on high-level (public) APIs intended for direct use by end-users.
Developers can thus grow the documentation organically within a single task-based workflow. As soon as a new feature/function is added - the developer need only include a docstring in their commit and it will reflect in the hosted page.
Markdown and ReST support
The pdoc framework renders Markdown in docstrings to HTML:
- Lists
- Are
- Supported
As are code blocks:
# Example invocation
result: Type = function(param="value", *variadic_args, **variadic_kwargs)
Data models
The pydantic framework has quickly become the leading
data validation library for Python.
It's not a stretch to say that there's a whole ecosystem being built around it with everything from web frameworks to data science toolkits using it as the base for their data models.
From a documentation perspective, if you can describe your data source as a pydantic derived
data model and then group them accordingly
such links could be fronted as data schemas. Standard representations such as "JSON Schema" can
be generated directly from pydantic models.
This also has advantages for testing.
Advanced tools
The pdoc framework is arguably the simplest auto-documentation tool for Python.
Below are some more advanced tools that are popular with large open-source projects:
Metadata
Release files for jambazid-rag 0.0.34
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 | |
|---|---|---|---|---|
| jambazid_rag-0.0.34.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jambazid_rag-0.0.34-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.1 kB
Release files / jambazid_rag-0.0.34.tar.gz
| Download URL | jambazid_rag-0.0.34.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3bc8c5fb7f555718a470131534be42801c7dfe669ec850693bfe8b15a6dc11b
|
|
BLAKE2b-256 checksum How to use checksums |
f2eaca33565d49bfab24ad945ae6e2edc8621e0214de7e975ce9be7e432a0db4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.2
|
Release files / jambazid_rag-0.0.34-py3-none-any.whl
| Download URL | jambazid_rag-0.0.34-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
813863aad486359e554ea919f912591daac4d988b96f2685890aa03e77ecc079
|
|
BLAKE2b-256 checksum How to use checksums |
3178705fa97135006019ba66a79da4b55dbec0469de018245a73f91f22b0c312
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.2
|
Security for jambazid-rag 0.0.34
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.