bazel: Builtin python rules have toolchain error at HEAD
Description of the bug:
Since 48eb0236b2f65babf3dd9c314069774a78b629a3, using py_test without using rules_python, results in a toolchain error:
ERROR: /Users/brentley/Developer/rules_xcodeproj/tools/params_processors/BUILD:55:8: While resolving toolchains for target //tools/params_processors:swift_debug_settings_processor_tests (ee6eec1): No matching toolchains found for types @@bazel_tools//tools/python:toolchain_type.
Which category does this issue belong to?
Python Rules
What’s the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
git checkout https://github.com/MobileNativeFoundation/rules_xcodeproj.git
cd rules_xcodeproj
USE_BAZEL_VERSION=last_green bazelisk build --nobuild //tools/params_processors:swift_debug_settings_processor_tests
Which operating system are you running Bazel on?
macOS 14.1.1
What is the output of bazel info release?
No response
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
No response
What’s the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?
No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
48eb0236b2f65babf3dd9c314069774a78b629a3
Have you found anything relevant by searching the web?
https://github.com/bazelbuild/bazel/issues/20315
Any other information, logs, or outputs that you want to share?
No response
About this issue
- Original URL
- State: closed
- Created 7 months ago
- Comments: 17 (14 by maintainers)
Commits related to this issue
- Add rules_python dep Workaround for https://github.com/bazelbuild/bazel/issues/20458 — committed to keith/rules_multirun by keith 7 months ago
- Add rules_python dep (#27) Workaround for https://github.com/bazelbuild/bazel/issues/20458 — committed to keith/rules_multirun by keith 7 months ago
- python: Make bazel_tools register system Python toolchain A regression from upgrading to rules_python 0.22.0 is that a Python toolchain is no longer registered by default (the prior 0.4.0 version reg... — committed to rickeylev/bazel by rickeylev 7 months ago
- python: Make bazel_tools register system Python toolchain A regression from upgrading to rules_python 0.22.0 is that a Python toolchain is no longer registered by default (the prior 0.4.0 version reg... — committed to rickeylev/bazel by rickeylev 7 months ago
- Force rules_python to use version 0.24.0. This version registers the python toolchains needed by rules_pkg and others. Fixes #161. Related to https://github.com/bazelbuild/bazel/issues/20458 — committed to katre/rules_java by katre 6 months ago
- Force rules_python to use version 0.24.0. Copybara Import from https://github.com/bazelbuild/rules_java/pull/162 BEGIN_PUBLIC Force rules_python to use version 0.24.0. (#162) This version registers... — committed to bazelbuild/rules_java by katre 6 months ago
- fix: register autodetecting toolchain automatically @bazel_tools depends on rules_python, but the version is currently specifies (0.22.0) doesn't register a toolchain by default. This means the Bazel... — committed to rickeylev/rules_python by rickeylev 6 months ago
Thinking more on this, I think this needs to be fixed, or the python rules shouldn’t be exposed from Bazel anymore. If I have to add a dep on rules_python to use the python rules, then we should just make people use those rules, right?