Skip to content

chore: use direct @dev_pip targets instead of requirement()#3798

Merged
rickeylev merged 1 commit into
bazel-contrib:mainfrom
rickeylev:update-bazel-python-deps-20260527
May 27, 2026
Merged

chore: use direct @dev_pip targets instead of requirement()#3798
rickeylev merged 1 commit into
bazel-contrib:mainfrom
rickeylev:update-bazel-python-deps-20260527

Conversation

@rickeylev
Copy link
Copy Markdown
Collaborator

Use @dev_pip// format instead of the requirement() macro. This aligns with modern bzlmod patterns and simplifies the BUILD file.

Use @dev_pip//<pkg> format instead of the requirement() macro. This aligns with modern bzlmod patterns and simplifies the BUILD file.
@rickeylev rickeylev requested a review from aignas as a code owner May 27, 2026 07:31
@rickeylev rickeylev enabled auto-merge May 27, 2026 07:32
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates docs/BUILD.bazel by removing the requirement macro load from @dev_pip//:requirements.bzl and refactoring the dependencies of sphinx_build_binary to use direct labels (e.g., @dev_pip//myst_parser) instead of the macro. The dependencies have also been sorted alphabetically. There are no review comments, and I have no additional feedback to provide.

@rickeylev
Copy link
Copy Markdown
Collaborator Author

I pulled this out of your uv.lock PR. Those requirement() calls have bugged me for awhile, so i figured a good time to kill them.

@rickeylev rickeylev added this pull request to the merge queue May 27, 2026
Merged via the queue into bazel-contrib:main with commit 733f240 May 27, 2026
5 checks passed
@rickeylev rickeylev deleted the update-bazel-python-deps-20260527 branch May 27, 2026 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants