| commit | dbc6c0431b074f6d9953c565266f73c68a444b6f | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Wed Jul 31 20:58:00 2024 -0700 |
| committer | GitHub <noreply@github.com> | Thu Aug 01 03:58:00 2024 +0000 |
| tree | 6f1282ba549a1feaa921f4bdc8ec13a83144a47c | |
| parent | ff1dfeda76a7843b6018bd2d702ba6ad2492c90b [diff] |
tests: make toolchain tests run in the same build instead of bazel-in-bazel integration tests (#2095) This changes the //tests/toolchains tests to run in the same Bazel build instance instead of being bazel-in-bazel integration tests. This is done by using a transition to set the python version to match the desired toolchain. This makes running the tests **much** cheaper -- there were 37 sub-bazel processes being started (one for each python version), which was very expensive. Debugging is also much easier because they aren't part of a bazel-in-bazel invocation.
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.