| commit | b3862ec2446dc9c21e1ff5a25f86105d7718975a | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Sat Sep 14 22:20:01 2024 -0700 |
| committer | GitHub <noreply@github.com> | Sun Sep 15 05:20:01 2024 +0000 |
| tree | 71b126d0e783e0f9da99a0eb389e0b7a7ac15a0e | |
| parent | 3f20b4b274753e116078f92b2aee92d8da4b3d88 [diff] |
docs: give some general guidance on how to define custom toolchains (#2220) From the discussion in #2216, it's clear that some better docs are needed to help people figure out how to define a toolchain and what the different pieces me. This gives some more explanation of the toolchain types, what they do, and how to define them. Along the way: * Add some more bazel objects to the inventory * Fix attribute lookups in the bazel inventory * Allow using parens in crossrefs, e.g. `foo()`
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.