| commit | 711186f144af06b431bd416b2d742874de3a2dea | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Thu Jan 18 15:47:04 2024 -0800 |
| committer | GitHub <noreply@github.com> | Thu Jan 18 15:47:04 2024 -0800 |
| tree | 0f69d6ae68d3a64fd8c58b5a6be7118439913334 | |
| parent | 6607a4ae4f680af879a0148e95a7ea78eca9dafa [diff] |
refactor: broaden visibility and use list() instead of keys() (#1704) This upstreams a couple trivial Google patches to make rules_python more compatible with some Google-internal changes. * Use list(dict) instead of dict.keys(). This is because some bzl files are run through a Python-based testing framework, and dict.keys() can't be concatenated to a list in Python 3. * Expand visibility to all of rules_python instead of just the python subdirectory. This makes some patches that use internals easier to maintain, but also makes the visiblity more in line with the rest of the project (where `//:__subpackages__` is used for convenience, as it avoids having to change visibility frequently, but still prevents public dependencies).
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.
Currently, the core rules build into the Bazel binary, and the symbols in this repository are simple aliases. However, we are migrating the rules to Starlark and removing them from the Bazel binary. Therefore, the future-proof way to depend on Python rules is via this repository. SeeMigrating from the Bundled Rules below.
The core rules are stable. Their implementation in Bazel is subject to Bazel's backward compatibility policy. Once migrated to rules_python, they may evolve at a different rate, but this repository will still 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.