Skip to content

Commit 2b6308c

Browse files
authored
tests: don't restrict python versions in bzlmod example (bazel-contrib#2362)
Under Bazel 8, the bzlmod example is failing because newer versions of some dependencies request Python 3.8 to be available. To fix, just comment out the restriction in the example. The example has a somewhat large dependency footprint, so enforcing this restriction seems untenable. The config is left commented out so users can discover the feature. Fixes bazel-contrib#2361 Fixes bazelbuild/bazel-central-registry#3056
1 parent f40038e commit 2b6308c

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

examples/bzlmod/MODULE.bazel

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -40,14 +40,16 @@ python.toolchain(
4040
# One can override the actual toolchain versions that are available, which can be useful
4141
# when optimizing what gets downloaded and when.
4242
python.override(
43-
available_python_versions = [
44-
"3.10.9",
45-
"3.9.18",
46-
"3.9.19",
47-
# The following is used by the `other_module` and we need to include it here
48-
# as well.
49-
"3.11.8",
50-
],
43+
# NOTE: These are disabled in the example because transitive dependencies
44+
# require versions not listed here.
45+
# available_python_versions = [
46+
# "3.10.9",
47+
# "3.9.18",
48+
# "3.9.19",
49+
# # The following is used by the `other_module` and we need to include it here
50+
# # as well.
51+
# "3.11.8",
52+
# ],
5153
# Also override the `minor_mapping` so that the root module,
5254
# instead of rules_python's defaulting to the latest available version,
5355
# controls what full version is used when `3.x` is requested.

0 commit comments

Comments
 (0)