Modernize packaging, tooling, and docs for ec_tools#10
Conversation
indestinee
commented
Feb 11, 2026
- Migrate to pyproject.toml + uv.lock, drop setup.py, add .python-version.
- Refresh README.md with usage examples, layout, and development notes.
- Tidy exports via all, minor formatting tweaks, and requirements update (add colorama).
- Update pre-commit hooks and configs; clean trailing blank lines.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 77b29bfa2a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ] | ||
|
|
||
| [tool.setuptools.packages.find] | ||
| where = ["ec_tools"] |
There was a problem hiding this comment.
Discover packages from the project root
Setting where = ["ec_tools"] makes setuptools search inside the ec_tools/ directory as the package root, so the built distribution will not include the top-level ec_tools package (it resolves subpackages like data, database, etc. as top-level names instead). In an installed wheel/sdist, imports used throughout this repo and README (for example import ec_tools.database) will fail, which breaks consumers after publishing.
Useful? React with 👍 / 👎.