|
| 1 | +# ✅ Python Package Development Checklist |
| 2 | + |
| 3 | +A checklist to ensure quality, maintainability, and usability of your Python package. |
| 4 | + |
| 5 | +--- |
| 6 | + |
| 7 | +## 1. Purpose & Scope |
| 8 | + |
| 9 | +- [ ] Clear purpose and use cases defined |
| 10 | +- [ ] Scoped to a specific problem/domain |
| 11 | +- [ ] Project name is meaningful and not taken on PyPI |
| 12 | + |
| 13 | +--- |
| 14 | + |
| 15 | +## 2. Project Structure |
| 16 | + |
| 17 | +- [ ] Uses `src/` layout or appropriate flat structure |
| 18 | +- [ ] All package folders contain `__init__.py` |
| 19 | +- [ ] Main configuration handled via `pyproject.toml` |
| 20 | +- [ ] Includes standard files: `README.md`, `LICENSE`, `.gitignore`, `CHANGELOG.md` |
| 21 | + |
| 22 | +--- |
| 23 | + |
| 24 | +## 3. Dependencies |
| 25 | + |
| 26 | +- [ ] All dependencies declared in `pyproject.toml` or `requirements.txt` |
| 27 | +- [ ] Development dependencies separated from runtime dependencies |
| 28 | +- [ ] Uses minimal, necessary dependencies only |
| 29 | + |
| 30 | +--- |
| 31 | + |
| 32 | +## 4. Code Quality |
| 33 | + |
| 34 | +- [ ] Follows PEP 8 formatting |
| 35 | +- [ ] Imports sorted with `isort` or `ruff` |
| 36 | +- [ ] No linter warnings (`ruff`, `flake8`, etc.) |
| 37 | +- [ ] Fully typed using `typing` module |
| 38 | +- [ ] No unresolved TODOs or FIXME comments |
| 39 | + |
| 40 | +--- |
| 41 | + |
| 42 | +## 5. Function & Module Design |
| 43 | + |
| 44 | +- [ ] Functions are small, pure, and single-responsibility |
| 45 | +- [ ] Classes follow clear and simple roles |
| 46 | +- [ ] Global state is avoided |
| 47 | +- [ ] Public API defined explicitly (e.g. via `__all__`) |
| 48 | + |
| 49 | +--- |
| 50 | + |
| 51 | +## 6. Documentation |
| 52 | + |
| 53 | +- [ ] `README.md` includes overview, install, usage, contributing |
| 54 | +- [ ] All functions/classes include docstrings (Google/NumPy style) |
| 55 | +- [ ] API reference documentation auto-generated (e.g., Sphinx, MkDocs) |
| 56 | +- [ ] Optional: `docs/` folder for additional documentation or site generator |
| 57 | + |
| 58 | +--- |
| 59 | + |
| 60 | +## 7. Testing |
| 61 | + |
| 62 | +- [ ] Unit and integration tests implemented |
| 63 | +- [ ] Test coverage > 80% verified by `coverage` |
| 64 | +- [ ] Tests are fast and deterministic |
| 65 | +- [ ] Continuous Integration (CI) configured to run tests |
| 66 | + |
| 67 | +--- |
| 68 | + |
| 69 | +## 8. Versioning & Releases |
| 70 | + |
| 71 | +- [ ] Uses semantic versioning (MAJOR.MINOR.PATCH) |
| 72 | +- [ ] Git tags created for releases |
| 73 | +- [ ] `CHANGELOG.md` updated with each release |
| 74 | +- [ ] Local build verified (`poetry build`, `hatch build`, or equivalent) |
| 75 | +- [ ] Can be published to PyPI and/or TestPyPI |
| 76 | + |
| 77 | +--- |
| 78 | + |
| 79 | +## 9. CLI or Scripts (Optional) |
| 80 | + |
| 81 | +- [ ] CLI entrypoint works correctly (`__main__.py` or `entry_points`) |
| 82 | +- [ ] CLI provides helpful messages (`--help`) and handles errors gracefully |
| 83 | + |
| 84 | +--- |
| 85 | + |
| 86 | +## 10. Examples / Tutorials |
| 87 | + |
| 88 | +- [ ] Usage examples included in `README.md` or `examples/` |
| 89 | +- [ ] Optional: Jupyter notebooks with demonstrations |
| 90 | +- [ ] Optional: Colab or Binder links for live usage |
| 91 | + |
| 92 | +--- |
| 93 | + |
| 94 | +## 11. Licensing & Attribution |
| 95 | + |
| 96 | +- [ ] LICENSE file included (MIT, Apache 2.0, GPL, etc.) |
| 97 | +- [ ] Author and contributors credited in `README.md` |
| 98 | +- [ ] Optional: `CITATION.cff` file for academic citation |
| 99 | + |
| 100 | +--- |
| 101 | + |
| 102 | +> You can duplicate this file for each new package or use it as a GitHub issue template for release checklists. |
0 commit comments