Autodocstring
I made this tool to improve code quality without much headache.
Have GEMINI_API_KEY defined in your PATH. You can do this by following these steps.
pip install autodocstring
Run this to generate docstrings to all your public methods at the desired python module.
autodocstring path/to/file
You may also want to target specific methods by using the --methodsparameter. The tool generates a backup file by default.
1 maintainer
Metadata
1 maintainer
Release files for autodocstring 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| autodocstring-0.1.2.tar.gz | 4.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autodocstring-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.8 kB
Release files / autodocstring-0.1.2.tar.gz
| Download URL | autodocstring-0.1.2.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ffd9e20751d25ce6053658c9a2455996617bbaf8e133e1a78a1e0ee8a8c456cb
|
|
BLAKE2b-256 checksum How to use checksums |
1b169db579dca1291dc06bc1a729b77ff0fa6407543ac8b6ec68ac2bf1446762
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Jan 8, 2025.
Transparency logRelease files / autodocstring-0.1.2-py3-none-any.whl
| Download URL | autodocstring-0.1.2-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa7d700b8dda1468c30e5d2103e11a35d4fbf9e29b1b4e983d19028fb2bf567c
|
|
BLAKE2b-256 checksum How to use checksums |
5c00c04c59ce43ed025c743574d565ce3d06fe691a06695ef71fa0ceda70b915
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Jan 8, 2025.
Transparency log
