Skip to content

Set up Python packaging and release process - #9

Merged
tmgsr02 merged 2 commits into
masterfrom
codex/configure-build-system-for-packaging
Oct 24, 2025
Merged

tmgsr02 merged 2 commits into
masterfrom
codex/configure-build-system-for-packaging

Conversation

@tmgsr02

@tmgsr02 tmgsr02 commented Oct 24, 2025

Copy link
Copy Markdown
Owner

Summary

  • configure setuptools-based build in pyproject.toml so wheels and sdists can be produced
  • expose a canonical version attribute and configure bump2version for managed releases
  • document release workflow, changelog, and packaging instructions in README and docs

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

@tmgsr02
tmgsr02 merged commit 6838724 into master Oct 24, 2025
0 of 8 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread pyproject.toml
Comment on lines +53 to +54
[tool.setuptools.package-data]
"tools.bench" = ["*.conf", "*.txt", "matplotlibrc"]

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant