commit | 1b3698334adb6290956fc6735217e3f9616bbb08 | [log] [tgz] |
---|---|---|
author | Alex Eagle <alex@aspect.dev> | Thu Jul 17 10:22:22 2025 -0700 |
committer | GitHub <noreply@github.com> | Thu Jul 17 10:22:22 2025 -0700 |
tree | fbce1ffc7d17264a36bfd97dabdd4db2b5eead54 | |
parent | 2c7187d6558ce39e1bd2fea4c0637722258f7790 [diff] |
gazelle_manifest: print the wrong hash when encountered Ideally developers should always re-run the manifest generator, which will update the hash for them. However I've got clients where the CI system is the only place that all the dependencies can resolve, either because of credentials needed to access the wheelhouse/PyPI, or because of disk exhaustion from massive wheels. Printing the difference allows a red PR to be greened up just by reading the CI log.
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.