| commit | a5076736b0d46b28146e7524f1c0d158d7ed3c2f | [log] [tgz] |
|---|---|---|
| author | Oleh Prypin <oprypin@google.com> | Fri Sep 06 05:23:38 2024 +0200 |
| committer | GitHub <noreply@github.com> | Fri Sep 06 03:23:38 2024 +0000 |
| tree | 4e1639b1185d2d8e2a8d382fb4c9b85bc5fb7f6d | |
| parent | 53f7407bdfd0e02c9f048a9e83f6acf0c9549099 [diff] |
feat(rules): add build_data_file field to PyExecutableInfo (#2181) PyExecutableInfo was added in https://github.com/bazelbuild/rules_python/pull/2166 with the field `runfiles_without_exe` that intentionally excludes files that are specific to that target/executable, such as the build data file (which may contain the target name, or other target-specific information). However, consuming tools (such as ones used within Google) may need to derive a file from that build data, override it completely, or be happy with its content as is. To aid that case, expose it via PyExecutableInfo.
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.