| commit | 54c9fab03af56869ac5b36fb2ab614a63a40a7ab | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Sat Aug 31 07:19:47 2024 -0700 |
| committer | GitHub <noreply@github.com> | Sat Aug 31 14:19:47 2024 +0000 |
| tree | 641186a74b4f406526d7033f8cc123eeb385dbcd | |
| parent | 4f2dd2f049dcc3656b6bc6e0995fbe0c6bd6d61b [diff] |
refactor(flags): return FeatureFlagInfo in --python_version flag (#2167) Make the `--python_version` flag also return the `FeatureFlagInfo` provider. There are two reasons to also return the FeatureFlagInfo provider: First, it allows the flag implementation to change the value and have that value respected by config_setting() later. This allows, for example, the rule to use custom logic (and information from things it depends on) to determine the effective flag value. Secondly, it makes the flag compatible with the Google fork of this rule, which is implemented using FeatureFlagInfo, to help eventually converge them. Along the way, add config_common to the Sphinx Bazel 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.