You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, the exact same configuration works in rules_python 1.3.0.
Description
The whl library BUILD generation has broken templating in rules_python 1.4.0-rc0 and later, leading to templating such as:
external/pip/aiocsv/BUILD.bazel:5:12: error loading package '@@pip_aiocsv//': Unable to find package for @@pip_//:config.bzl: The repository '@@pip_' could not be resolved: Repository '@@pip_' is not defined. and referenced by '@@pip//aiocsv:whl'
Bazel 7.6.1, bzlmod enabled, but rules_python still used via WORKSPACE.
🔥 Exception or Error
external/pip/aiocsv/BUILD.bazel:5:12: error loading package '@@pip_aiocsv//': Unable to find package for @@pip_//:config.bzl: The repository '@@pip_' could not be resolved: Repository '@@pip_' is not defined. and referenced by '@@pip//aiocsv:whl'
🐞 bug report
Affected Rule
generate_whl_library_build_bazel
Is this a regression?
Yes, the exact same configuration works in rules_python 1.3.0.
Description
The whl library BUILD generation has broken templating in rules_python 1.4.0-rc0 and later, leading to templating such as:
Resulting BUILD file:
notice the templating error at second load
🔬 Minimal Reproduction
Bazel 7.6.1, bzlmod enabled, but rules_python still used via WORKSPACE.
🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules_python version:
Anything else relevant?
Looks like this was introduced in #2781
rules_python/python/private/pypi/generate_whl_library_build_bazel.bzl
Lines 62 to 72 in 9e613d5
The text was updated successfully, but these errors were encountered: