| commit | da23db5b4dc095c597a0fc792f04e7ff50d37142 | [log] [tgz] |
|---|---|---|
| author | Josh Cannon <joshdcannon@gmail.com> | Mon Nov 17 23:13:13 2025 -0600 |
| committer | GitHub <noreply@github.com> | Tue Nov 18 05:13:13 2025 +0000 |
| tree | 21226632647975cf76eabe8f9e25b2cb5a471834 | |
| parent | 3440572f5d8bcb45df8db93ecc102475d6508bee [diff] |
refactor(gazelle): Generate a modules map per wheel, then merge (#3415) This change internally splits modules mapping generation to be per-wheel, with a final quick "merge" action at the end. The idea is to make this process both concurrent and cached (courtesy of Bazel), which can be ideal for codebases with a large set of requirements (as many monorepos end up doing) Note that the `generator.py` interface changed. This seemed internal, so I didn't mark it breaking (but this change could actually just leave the generator alone, since the current implementation is fine with 1 wheel). I ran this on the work repo and saw no change in output (but as I edited a single requirement, the overall process was fast ⚡ )
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.