Repository navigation
Set up Python packaging and release process - #9
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ 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.package-data] | ||
| "tools.bench" = ["*.conf", "*.txt", "matplotlibrc"] |
There was a problem hiding this comment.
Include non-Python bench resources in the package
The packaging configuration only ships *.conf, *.txt, and matplotlibrc files from tools.bench, but the benchmarking scripts load YAML and JSON templates from subdirectories such as tools/bench/experiments and tools/bench/contextual. Building a wheel from this configuration will omit those resources, so any installed copy of the package will fail when a script tries to read tools/bench/.../*.yaml or .json. Please expand the package-data patterns (e.g., include **/*.yaml and **/*.json) so that the packaged artifacts contain the files the runtime code expects.
Useful? React with 👍 / 👎.
Summary
Testing
python -m pip install --user build(fails: ProxyError prevents downloading build package)python -m build(fails: No module named build because build could not be installed)https://chatgpt.com/codex/tasks/task_e_68fade2106f883209f12dedf9d7460bd