| commit | e8dcfefe5534afbf8cd17aa944be0db8f1be20a3 | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Thu Jun 20 12:22:33 2024 -0700 |
| committer | GitHub <noreply@github.com> | Thu Jun 20 19:22:33 2024 +0000 |
| tree | 0c19a1d28726f96be6591850e2a70c9042ad0407 | |
| parent | 0b6b471f18382456bec3a292585ea38b71770ad4 [diff] |
refactor: lookup exec interpreter using toolchain resolution (#1997) This changes the exec tools toolchain to use toolchain resolution to find the interpreter. The main benefit of this is it avoids having to duplicate specifying where the interpreter is. Instead, it is automatically found by toolchain resolution.
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.
Currently, the core rules build into the Bazel binary, and the symbols in this repository are simple aliases. However, we are migrating the rules to Starlark and removing them from the Bazel binary. Therefore, the future-proof way to depend on Python rules is via this repository. SeeMigrating from the Bundled Rules below.
The core rules are stable. Their implementation in Bazel is subject to Bazel's backward compatibility policy. Once migrated to rules_python, they may evolve at a different rate, but this repository will still 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.