| commit | 981087023b560e1daa17350840396656dca3834f | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Wed Dec 20 09:13:36 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Dec 20 09:15:20 2023 -0800 |
| tree | 0ba2406db7cff59e5daddd19fca7176f12d8f4da | |
| parent | f849dc414fbe4503bc401a52d30dd8e829c93041 [diff] |
python: rules_python 0.22.0 -> 0.22.1 soas to register Python toolchain by default 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 registered the "autodetecting" toolchain). Subsequent versions of rules_python (0.23.0 or later) register a toolchain by default again, but it's a downloaded runtime, which makes upgrading more involved. To fix, upgrade to 0.22.1, which registers the autodetecting toolchain. This restores the rules_python 0.4.0 behavior and should suffice until bazel_tools is upgraded to 0.23.0 or later. Fixes https://github.com/bazelbuild/bazel/issues/20458 Closes https://github.com/bazelbuild/bazel/pull/20514 PiperOrigin-RevId: 592578175 Change-Id: I707a4c96829063536f81cc10e144652102da1e7e
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
