fix: make executable implicit defaults public so other modules can use rule builders (#3919) (#3970) Backports #3919 to `release/1.9` (requested by @aignas / @rickeylev). `create_executable_rule_builder()` (used by `py_binary_rule_builder()` / `py_test_rule_builder()`, the public `python/api/executables.bzl` API) bundles three implicit attrs whose defaults point at private targets under `//python/private`. These had no explicit visibility, so any external module constructing a rule via the builder API failed at analysis time with a visibility error. Commits: - `fix: make executable implicit defaults public ... (#3919)` — cherry-pick of `19ffd215`, unchanged from main. - `Release 1.9.2: Update changelog` — finalizes the changelog entry (`release/1.9` doesn't carry the `news/` fragment infra main uses, so the fragment is folded into `CHANGELOG.md` directly, matching #3775/#3776/#3819). Fixes #3919 on `1.9.x`. --------- Co-authored-by: Richard Levasseur <richardlev@gmail.com>
This repository is the home of the core Python rules -- py_library, py_binary, py_test, 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.