Skip to content

refactor(examples): migrate remaining lockfiles to uv lock() - #4365

Merged
rickeylev merged 1 commit into
bazel-contrib:mainfrom
rickeylev:use_uv_lock_rule
Oct 27, 2026
Merged

rickeylev merged 1 commit into
bazel-contrib:mainfrom
rickeylev:use_uv_lock_rule

Conversation

@rickeylev

Copy link
Copy Markdown
Collaborator

Now that the uv lock() macro supports WORKSPACE builds, remaining
non-dedicated compile_pip_requirements targets and pip-compile
lockfiles can use uv instead.

Migrate tests/multiple_inputs to lock() with diff_test, register
uv toolchains in the example WORKSPACE and MODULE.bazel files, and
regenerate the example requirements*.txt files with uv.

Now that the `uv` `lock()` macro supports `WORKSPACE` builds, remaining
non-dedicated `compile_pip_requirements` targets and `pip-compile`
lockfiles can use `uv` instead.

Migrate `tests/multiple_inputs` to `lock()` with `diff_test`, register
`uv` toolchains in the example `WORKSPACE` and `MODULE.bazel` files, and
regenerate the example `requirements*.txt` files with `uv`.
@rickeylev

Copy link
Copy Markdown
Collaborator Author

AI Disclosure:

  • Human oversight: semi-autonomous — directed and reviewed by a human maintainer (@rickeylev).
  • Review comment handling: The human author and AI agent monitor and respond to review comments, with human review and approval of changes.

This is an automatically generated agent comment.

@dougthor42 dougthor42 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Should we keep some non-uv examples in case people want slow stuff? Or in case uv becomes enshittified and people want to switch back?

@rickeylev

Copy link
Copy Markdown
Collaborator Author

I think we should keep the docs and tests as long as we support it.

I'm torn about what compile_pip_requirement's future is, though. I like the idea of supporting all the different lockers (pycross supports some other lockers), however, we need owners who are interested in supporting them.

@rickeylev
rickeylev added this pull request to the merge queue Oct 27, 2026
Merged via the queue into bazel-contrib:main with commit 8ca9a77 Oct 27, 2026
13 checks passed
@rickeylev
rickeylev deleted the use_uv_lock_rule branch October 27, 2026 18:35
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