| commit | bc8658ae6ed6750d07ed4b7d6ba58f0951fc68e5 | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Mon Dec 02 16:00:26 2024 -0800 |
| committer | GitHub <noreply@github.com> | Tue Dec 03 00:00:26 2024 +0000 |
| tree | 94fcc83c4577a6b133583818d6ea5996f92b36e7 | |
| parent | a36233950d887a4932537dc7831544d2608d1d9b [diff] |
docs: mention calling register_toolchains in custom toolchain docs (#2463) Mention where register_toolchains() should be when defining custom toolchains. Also link to the Bazel docs about toolchains. This stems from Slack discussion where someone was trying to define custom toolchains and got hung up on the last step or registering them.
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.