Confirm this is a feature request for the Python library and not the underlying OpenAI API.
Describe the feature or improvement you're requesting
Is your feature request related to a problem? Please describe.
Rye has been officially deprecated, with its features fully integrated into uv by the Astral team. Keeping [tool.rye] blocks and legacy Rye actions in CI/CD pipelines introduces technical debt. Migrating to native uv toolchains will optimize local development workflows and significantly accelerate GitHub Actions runner build times.
Describe the solution you'd like
I would love to submit a PR to migrate the repository infrastructure over to uv. The changes include:
pyproject.toml: Remove [tool.rye] blocks, map dev-dependencies to standard [dependency-groups], and translate task sequences under [tool.rye.scripts] into native [tool.uv.scripts] composite tasks.- Lockfiles: Remove
requirements.lock and requirements-dev.lock, replacing them with a single, optimized uv.lock.
- CI/CD Workflows: Update
.github/workflows/ files to replace legacy Rye installation steps with the official astral-sh/setup-uv action to leverage faster built-in caching.
- Documentation: Refresh the development setup commands in
CONTRIBUTING.md and README.md.
Describe alternatives you've considered
Leaving the project on Rye, but given its end-of-life status, migrating to uv ensures long-term maintenance and compatibility with upcoming Python releases.
Additional context
I have already validated the dependency group mappings and composite task configurations locally. If this looks good to the maintainers, please assign it to me and I can open a clean, fully tested PR right away!
Additional context
No response
Confirm this is a feature request for the Python library and not the underlying OpenAI API.
Describe the feature or improvement you're requesting
Is your feature request related to a problem? Please describe.
Rye has been officially deprecated, with its features fully integrated into
uvby the Astral team. Keeping[tool.rye]blocks and legacy Rye actions in CI/CD pipelines introduces technical debt. Migrating to nativeuvtoolchains will optimize local development workflows and significantly accelerate GitHub Actions runner build times.Describe the solution you'd like
I would love to submit a PR to migrate the repository infrastructure over to
uv. The changes include:pyproject.toml: Remove[tool.rye]blocks, map dev-dependencies to standard[dependency-groups], and translate task sequences under[tool.rye.scripts]into native[tool.uv.scripts]composite tasks.requirements.lockandrequirements-dev.lock, replacing them with a single, optimizeduv.lock..github/workflows/files to replace legacy Rye installation steps with the officialastral-sh/setup-uvaction to leverage faster built-in caching.CONTRIBUTING.mdandREADME.md.Describe alternatives you've considered
Leaving the project on Rye, but given its end-of-life status, migrating to
uvensures long-term maintenance and compatibility with upcoming Python releases.Additional context
I have already validated the dependency group mappings and composite task configurations locally. If this looks good to the maintainers, please assign it to me and I can open a clean, fully tested PR right away!
Additional context
No response