| commit | 612baef1f14d1af89594f45559bc9c11a50d390a | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Wed Sep 04 20:50:27 2024 -0700 |
| committer | GitHub <noreply@github.com> | Thu Sep 05 03:50:27 2024 +0000 |
| tree | 66ce171c8f8a0f5280e67ee9397f1c6b6d550bfb | |
| parent | fe1d9a706e542053128d6d540da1fc32926677fe [diff] |
tests: move various supporting code under tests/support (#2183) tests: move various supporting code under tests/support * Move subject classes under support * Switch to using rules_testing DefaultInfo subject * Move fake cc toolchains under tests/support/cc_toolchains (these are used in several places, not just tests/cc) * Make literal references of old //tests/cc locations use the constants from support.bzl This is both for code clarity (support code being in a common location), but also to make it easier to import the support code for the subset of tests Google imports and runs.
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.