chore: migrate requirements.in files to pyproject.toml - #4099
Merged
rickeylev merged 5 commits intoAug 23, 2026
Conversation
Standardize Python dependency declarations across tools, examples, and tests to use standard pyproject.toml configuration instead of requirements.in files. Replace requirements.in inputs with pyproject.toml, update corresponding BUILD.bazel and documentation references, and regenerate all associated requirement lockfiles and Gazelle manifests.
Sync with upstream/main and resolve merge conflicts by updating migrated pyproject.toml files and regenerating all affected requirements lockfiles and Gazelle manifests.
Sync Windows requirement lockfiles with pyproject.toml inputs to resolve CI test failures. Update comment headers and package provenance annotations in Windows lockfiles across examples and gazelle to reference pyproject.toml instead of requirements.in.
Sync with upstream/main and resolve merge conflicts by updating migrated pyproject.toml files and regenerating all affected requirements lockfiles (both Linux and Windows).
rickeylev
marked this pull request as ready for review
August 23, 2026 06:28
rickeylev
enabled auto-merge
August 23, 2026 06:55
aignas
approved these changes
Aug 23, 2026
aignas
left a comment
aignas
left a comment
Collaborator
There was a problem hiding this comment.
I think we have one place where we have integration tests checking that we can consume requirements.in, so this is a great start to cleanup the codebase.
Thank you!
Collaborator
Author
|
Yes, feels good to clean this up. I'm going start another PR to switch them over to the uv-based locking next. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Standardize Python dependency declarations across tools, examples, and
tests to use standard pyproject.toml configuration instead of
requirements.in files.
Replace requirements.in inputs with pyproject.toml, update corresponding
BUILD.bazel and documentation references, and regenerate all associated
requirement lockfiles and Gazelle manifests.