Lazynote 🚀✨
Lazynote is an AI-powered tool that can automatically generate documentation comments for classes, modules, and packages. It also supports the translation and customization of existing comments. 💡📝
Features 🌟
- Automatic Generation: Automatically generate documentation comments for classes, modules, and packages by parsing the Python Abstract Syntax Tree (AST), feeding the relevant key code to AI, and using the Google Docstrings template to generate precise comments. 🛠️
- Smart Translation: Translate existing comments, supporting multiple languages. The input can be a Python package, module, or class. If it's a package, it will parse the syntax tree layer by layer, perform source code injection, and inject comments into the source code. 🌐
- Comment Polishing: Use AI technology to polish comments for improved readability. A small but powerful feature. 📖✨
- Flexible Customization: Easily customize all comments across the entire repository. This framework-level functionality has low-level API extensibility. 🔧
Installation 📦
You can easily install Lazynote using pip:
pip install lazynote
Quick Start 🚀
Here is a simple example demonstrating how to use Lazynote to automatically generate and manage documentation comments.
import pytest
from lazynote.manager import SimpleManager
manager = SimpleManager(pattern='fill')
manager.traverse(lazyllm_package.components,
skip_modules=['lazyllm.components.deploy.relay.server'])
Features Overview 📚
Lazynote provides the following modes to easily customize all comments across the entire repository using AI and source code:
- TRANSLATE: Translate existing comments. 🌍
- POLISH: Polish and optimize comments. 💅
- CLEAR: Clear existing comments. 🗑️
- FILL: Fill in missing comments. 📝
Documentation 📖
For more detailed information and advanced usage, please refer to our .
Contributing 🌟
Contributions are welcome! Please read CONTRIBUTING.md for more information. 💖
License 📄
This project is licensed under the MIT License. For more details, please refer to LICENSE. 📝
Metadata
Release files for lazynote 0.1.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 | Provenance | Actions |
|---|---|---|---|---|
| lazynote-0.1.4.tar.gz | 11.0 kB | Without provenance | Details for lazynote-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lazynote-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for lazynote-0.1.4-py3-none-any.whl |
Total release size: 24.1 kB
Release files / lazynote-0.1.4.tar.gz
| Download URL | lazynote-0.1.4.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4abfa68c6119f2989e7c0b12c80b4755eba61b74d2efb27ab74513d1f766a68f
|
|
BLAKE2b-256 checksum How to use checksums |
85aebf831b161733c8f129e0acfec38287eaf90c3aad55f25d910ea3dce43e0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.10.14 Linux/4.18.0-425.3.1.el8.x86_64
|
Release files / lazynote-0.1.4-py3-none-any.whl
| Download URL | lazynote-0.1.4-py3-none-any.whl |
|---|---|
| Size | 13.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f31c5907074da7b7c2ddb4ba3058a9f10c4f7fee1360dd2f1faeebbb8c368aaf
|
|
BLAKE2b-256 checksum How to use checksums |
2fbc46007d4abefdeb2aaaa9605a930b45e6aecb89c820a32d03f13f717bea4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.10.14 Linux/4.18.0-425.3.1.el8.x86_64
|
Security for lazynote 0.1.4
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.