Google Git
Sign in
fuchsia/third_party/github.com/bazelbuild/rules_python/refs/heads/upstream/main
commit
5511aaf1e95fbf6b3eeca64ad503b26d712f50aa
[log]
author
Ignas Anikevicius <240938+aignas@users.noreply.github.com>
Sun May 10 15:49:29 2026 +0900
committer
GitHub <noreply@github.com>
Sun May 10 06:49:29 2026 +0000
tree
5bed10671d9ecdcbf60feffd5cf12ee8de5839fe
parent
3871306fb4ca2a7abcf5029e89ad381095cb09b5 [diff]
fix(logger): do not output WARN level logs for non-root modules (#3760)

A user has reported issues which actually resulted from a particular
`bazel` version being used and once he updated, the issues disappeared
because of changes in implicit non-root module dependencies.

In order to reduce the warning spam of non-root modules, set the default
level to `ERROR` for non-root module parsing context and `WARN` for root
module context. This means that the users will not get console output
that they have no way to fix without patching upstream dependencies.

At the same time ensure that the name of the module is printed together
with the logs to better understand where something is coming from.

Fixes #3749

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
4 files changed
tree: 5bed10671d9ecdcbf60feffd5cf12ee8de5839fe
  1. .agents/
  2. .bazelci/
  3. .bcr/
  4. .ci/
  5. .github/
  6. command_line_option/
  7. docs/
  8. examples/
  9. gazelle/
  10. private/
  11. python/
  12. sphinxdocs/
  13. tests/
  14. tools/
  15. .bazelignore
  16. .bazelrc
  17. .bazelrc.deleted_packages
  18. .bazelversion
  19. .editorconfig
  20. .git-blame-ignore-revs
  21. .gitattributes
  22. .gitignore
  23. .pre-commit-config.yaml
  24. .python-version
  25. .readthedocs.yml
  26. addlicense.sh
  27. AGENTS.md
  28. AUTHORS
  29. BUILD.bazel
  30. BZLMOD_SUPPORT.md
  31. CHANGELOG.md
  32. CONTRIBUTING.md
  33. CONTRIBUTORS
  34. GEMINI.md
  35. internal_dev_deps.bzl
  36. internal_dev_setup.bzl
  37. LICENSE
  38. MODULE.bazel
  39. README.md
  40. RELEASING.md
  41. specialized_configs.bazelrc
  42. version.bzl
  43. WORKSPACE
  44. WORKSPACE.bzlmod
README.md

Python Rules for Bazel

Build status

Overview

This repository is the home of the core Python rules -- py_library, py_binary, py_test, 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.

Design

  • Supported OSes - as per our supported platform policy, we strive for support on all of the platforms that we have CI for. Some platforms do not have the same backwards compatibility guarantees, but we hope the community can step in where needed to make the support more robust.
  • requirements.txt is how users have been defining dependencies for a long time. We support this to support legacy usecases or package managers that we don't support directly. Any additional information that we need will be retrieved from the SimpleAPI during the bzlmod extension evaluation phase. Then it will be written to the MODULE.bazel.lock file for future reuse. We have plans to support uv.lock file directly. uv is recommended for generating a fully locked requirements.txt file and we do provide a rule for it.
  • The py_binary, py_test rules should scale to large monorepos and we work hard to minimize the work done during analysis and build phase. What is more, the space requirements for should be minimal, so we strive to use symlinks rather than extracting wheels at build time. This means that for different configurations of the same build, we are not extracting the wheel multiple times thus scaling better over the time. From 2.0 onwards we are creating a virtual env for each target by creating an actual minimal virtual environment using symlinks. We plan on creating the traditional site-packages layout in the future by default.
  • Support for standards - we strive to first implement any standards needed within rules_python and this has resulted in a few PEPs supported within pure starlark - PEP440, PEP509.

Common misconceptions:

  • rules_python has to keep backwards compatibility with google3. Whilst this might have been true in the past, rules_python is an open source project and any compatibility needs should come from the community - we have no requirement to keep this compatibility and are allowed to make our decisions. However, we do want to keep backwards compatibility as long as possible to not upset users with never ending migrations.
  • rules_python is not caching pip downloads. With 2.0, we use Bazel's downloader by default and rely on bazel to provide the repository caching mechanisms. This means that for simpler setups this should result in transparent and scalable caching with the most recent bazel versions unless there are issues in the bazel itself.

Documentation

For detailed documentation, see https://rules-python.readthedocs.io

Bzlmod support

See Bzlmod support for more details.