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

Bazel 8 support #132

Closed
blockjon-dd opened this issue Dec 10, 2024 · 3 comments · Fixed by #133
Closed

Bazel 8 support #132

blockjon-dd opened this issue Dec 10, 2024 · 3 comments · Fixed by #133

Comments

@blockjon-dd
Copy link

blockjon-dd commented Dec 10, 2024

Does rules_pycross support bazel 8? I tried it yesterday and I noticed my python integration did not work.

Here's the show stopper I'm getting:

ERROR: /home/builder/.cache/bazel/_bazel_builder/5ca5f6b08bf6f8bda395a366751f36b0/external/rules_pycross++toolchains+pycross_toolchains/BUILD.bazel:6:33: Illegal ambiguous match on configurable attribute "version" in @@rules_pycross++toolchains+pycross_toolchains//:_interpreter_version:
--
  | @@rules_python+//python/config_settings:is_python_3.11.10
  | @@rules_python+//python/config_settings:is_python_3.11.7
  | Multiple matches are not allowed unless one is unambiguously more specialized or they resolve to the same value. See https://bazel.build/reference/be/functions#select.
@blockjon-dd blockjon-dd changed the title Bazel 8 support? Bazel 8 support Jan 8, 2025
@betaboon
Copy link
Collaborator

betaboon commented Jan 13, 2025

@blockjon-dd do you know which rules_python-version you've been using for this?

I'm asking because i see the same behavior with bazel==7.4.1 + rules_python==1.0.0 + bzlmod

@betaboon
Copy link
Collaborator

just as an update. i think this has nothing to do with bazel 8 nor rules_python 1.0.0.

I can see similar behavior with bazel==7.4.1 + rules_python==0.37.0 + bzlmod when registering multiple python.toolchains when eg 3.11.7 is registered while 3.11.10 is the latest patch-level for that minor.

bisecting has uncovered this PR: bazelbuild/rules_python#2253
it has first been included in rules_python==0.37.0

@betaboon
Copy link
Collaborator

another update:
I've been able to reproduce the problem all the way down to rules_python==0.36.0.

bisecting has now uncovered this PR: bazelbuild/rules_python#2217 which actually seems related

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 a pull request may close this issue.

2 participants