[Bug]: Repository already generated.

[siscia]

What happened?

% bazel query '@pypi//...'
ERROR: /private/var/tmp/_bazel_simone/d5ca606f12ab6c659b9a7bb351339261/external/aspect_rules_py+/uv/private/extension.bzl:553:28: Traceback (most recent call last):
	File "/private/var/tmp/_bazel_simone/d5ca606f12ab6c659b9a7bb351339261/external/aspect_rules_py+/uv/private/extension.bzl", line 899, column 18, in _uv_impl
		_sbuild_repos(module_ctx, lock_specs, annotation_specs, override_specs)
	File "/private/var/tmp/_bazel_simone/d5ca606f12ab6c659b9a7bb351339261/external/aspect_rules_py+/uv/private/extension.bzl", line 553, column 28, in _sbuild_repos
		sdist_build(
Error in repository_rule: A repo named sbuild__pypi__default__aiohttp is already generated by this module extension at /private/var/tmp/_bazel_simone/d5ca606f12ab6c659b9a7bb351339261/external/aspect_rules_py+/uv/private/extension.bzl:553:28
ERROR: Target parsing failed due to unexpected exception: error evaluating module extension @@aspect_rules_py+//uv/unstable:extension.bzl%uv

I follow the instructions and added to our MODULE.bazel

...

uv = use_extension("@aspect_rules_py//uv/unstable:extension.bzl", "uv")
uv.declare_hub(
    hub_name = "pypi",      # Or whatever you wish
)
uv.declare_venv(
    hub_name = "pypi",      # Must be a declared hub
    venv_name = "default",  # Or whatever you wish
)
uv.lockfile(
    hub_name = "pypi",      # Must be a declared hub
    venv_name = "default",  # Must be a declared venv
    src = "//:uv.lock",
)
use_repo(uv, "pypi")

Version

Development (host) and target OS/architectures:

Output of bazel --version:

% bazel --version
bazel 8.4.2

Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:

# Aspect Rules Py - Enhanced Python rules
bazel_dep(name = "aspect_rules_py", version = "1.7.0")

# Override to use git repository since not yet in BCR
git_override(
    module_name = "aspect_rules_py",
    remote = "https://github.com/aspect-build/rules_py.git",
    commit = "f0667bd424ecbc1ef78b38a929d37d6aa21e636e",
)

Language(s) and/or frameworks involved:

Python

How to reproduce

#pyproject.toml
[project]
name = "foo"
description = "foo"
version = "0.2.0"
requires-python = ">=3.11.5,<=3.12.11"
authors = []
dependencies = [
    "aiohttp==3.12.13; python_full_version <= '3.11.5' or python_version >= '3.12'", # CoreApiCanary2 or py312 upgrade.
    "aiohttp==3.8.5; python_full_version > '3.11.5' and python_version < '3.12'", # Current prod on py311.
]

Any other information?

No response

[zsol]

Another typical situation this can arise in is accelerator-enabled libraries (torch, flash-attn, etc) where people will typically have two versions of the same package in the lockfile, and choose one based on the install platform (e.g. on macos they'd want a non-accelerated version of the package, but on linux they'd want the wheel with a specific cuda version - the accelerator typically exists as part of the package version today unfortunately).

In any case, the bug is that _whl_install_repo_name() and _sbuild_repo_name() should also encode the package's version into the repo name.

[arrdem]

Yeah, a specific case I want to look at is tensorflow which is not just conditional but the module named tensorflow is typically provided by entirely separate packages on MacOS vs Linux and some bridging will be required there.