Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(uv): move around uv implementation files #2580

Merged
merged 2 commits into from
Jan 26, 2025

Conversation

aignas
Copy link
Collaborator

@aignas aignas commented Jan 25, 2025

This PR starts establishing a structure that will eventually become a
part of our API. This is a prerequisite for #2578 which removes the
versions.bzl file in favour of a more dynamic configuration of the
extension. We also remove the defs.bzl to establish a one symbol per
file convention.

Things that I wish we could change is //python/uv:extensions.bzl and
the fact that we have extensions in the load path. I think it cannot
be removed, because that may break the BCR test. On the other hand,
maybe we could remove it and do an alpha release to verify this
assumption.

Work towards #1975

This PR starts establishing a structure that will eventually become a
part of our API. This is a prerequisite for bazelbuild#2578 which removes the
versions.bzl file in favour of a more dynamic configuration of the
extension. We also remove the `defs.bzl` to establish a one symbol per
file convention.

Things that I wish we could change is `//python/uv:extensions.bzl` and
the fact that we have `extensions` in the load path. I think it cannot
be removed, because that may break the BCR test. On the other hand,
maybe we could remove it and do an alpha release to verify this
assumption.

Work towards bazelbuild#1975
@aignas aignas requested a review from rickeylev as a code owner January 25, 2025 07:04
@aignas aignas added this pull request to the merge queue Jan 26, 2025
@rickeylev
Copy link
Collaborator

I think it should be OK for BCR because it sets dev_dependency. When BCR runs, it creates a root module that depends on the module-under-test/release. A way to check this would be to add a dev dep use_extension() of a non-existent path in rules_python, then run one of the examples.

Merged via the queue into bazelbuild:main with commit 18f76f9 Jan 26, 2025
4 checks passed
@aignas aignas deleted the refactor/uv-prep branch January 26, 2025 23:31
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