| commit | c2ff89f00f4e860cc79d169db07b3b8bedcf384f | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Sat Nov 22 03:47:38 2025 +0100 |
| committer | GitHub <noreply@github.com> | Sat Nov 22 02:47:38 2025 +0000 |
| tree | b6ad9cc92be168927116b2de45db910787d075e0 | |
| parent | 846dfd0c5699da8cc2e42067e8ccd0f5a1704328 [diff] |
fix: Avoid C++ toolchain requirement if possible (#2919) By making use of the new `launcher_maker_toolchain` in Bazel 9, rules_python can avoid the requirement for a C++ toolchain targeting the target platform if that platform isn't Windows. For example, this makes it possible to cross-compile pure Python targets from one Unix to another. Since Java targets have a dependency on Python targets through the `proguard_allowlister`, this also allows Java targets to be built without any C++ toolchain.
This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.
Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.
Examples live in the examples directory.
The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.
The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.
For detailed documentation, see https://rules-python.readthedocs.io
See Bzlmod support for more details.