| commit | 36bb556220458d4692cf84c504fa9563b7bebb79 | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Sun Sep 01 20:42:08 2024 -0700 |
| committer | GitHub <noreply@github.com> | Mon Sep 02 03:42:08 2024 +0000 |
| tree | d7b497acc1742c480245f670accc7f5a9a55cbd4 | |
| parent | b97a5d61138666a434ed69b480a175e5c03d9356 [diff] |
feat(rules): add PyExecutableInfo (#2166) The PyExecutableInfo provider exposes executable-specific information that isn't easily accessible outside the target. The main purpose of this provider is to facilitate packaging a binary or deriving a new binary based upon the original. Within rules_python, this will be used to pull the zip-building logic out of executables and into separate rules. Within Google, this will be used for a similar "package a binary" tool. Along the way: * Add runfiles references to sphinx inventory
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.