ANDROID: kleaf: fix 2-stage bootstrapping for recursive Python invocations.

For recursive Python invocations (e.g. Kleaf integration test, where
we have `bazel run <py_binary>` which calls another
`bazel run <py_binary>`), simply appending $venv_site_packages to
PYTHONPATH won't work because the `import _bazel_site_init` of the
inner py_binary will import the _bazel_site_init from the outer
py_binary. To make this working properly, record an OLDPYTHONPATH
variable so in the inner py_binary, we append $venv_site_packages
to OLDPYTHONPATH to form PYTHONPATH, removing the venv_site_packages
of the outer py_binary.

Bug: 438286001
Change-Id: I14197b7727065f9946ea7b32f7b13c09e3800e63
1 file changed
tree: d7c03cc490e0ba4d2800440d226cc363228f873e
  1. .bazelci/
  2. .bcr/
  3. .ci/
  4. .github/
  5. docs/
  6. examples/
  7. gazelle/
  8. private/
  9. python/
  10. sphinxdocs/
  11. tests/
  12. tools/
  13. .bazelignore
  14. .bazelrc
  15. .bazelversion
  16. .editorconfig
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .pre-commit-config.yaml
  21. .python-version
  22. .readthedocs.yml
  23. addlicense.sh
  24. AUTHORS
  25. BUILD.bazel
  26. BZLMOD_SUPPORT.md
  27. CHANGELOG.md
  28. CONTRIBUTING.md
  29. CONTRIBUTORS
  30. internal_dev_deps.bzl
  31. internal_dev_setup.bzl
  32. LICENSE
  33. METADATA
  34. MODULE.bazel
  35. MODULE_LICENSE_APACHE2
  36. OWNERS
  37. README.md
  38. RELEASING.md
  39. version.bzl
  40. WORKSPACE
  41. 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, 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.

Documentation

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

Bzlmod support

  • Status: Beta
  • Full Feature Parity: No

See Bzlmod support for more details.