perf: lazily load gazelle manifest files (#2746) In large repositories where Python may not be the only language, the gazelle manifest loading is done unnecessarily, and is done during the configuration walk. This means that even for non-python gazelle invocations (eg `bazel run gazelle -- web/`), Python manifest files are being parsed and loaded into memory. This issue compounds if the repository uses multiple dependency closures, ie multiple `gazelle_python.yaml` files. In our repo, we currently have ~250 Python manifests, so loading them when Gazelle is only running over other languages is time consuming. Co-authored-by: Douglas Thor <dougthor42@users.noreply.github.com>
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.