fix: add flag to use runtime venv creation when using bootstrap=script (#2590)

The bootstrap=script implementation was changed to use declare_symlink()
to create explicit
symlinks so its venv works. Unfortunately, this broke packaging rules,
which would treat
the symlinks as regular files.

To fix, introduce a flag that stops using declare_symlink() and instead
creates the venv
at runtime. Creating a venv at runtime is problematic for various
reasons, but this should
work well enough until packaging rules are able to handle these raw
symlinks.

The location of the venv can be somewhat controlled by setting the
`RULES_PYTHON_VENVS_ROOT`
environment variable. This is to better accommodate cases where using
/tmp is problematic.

Along the way, sort the environment variable docs by their name.

Fixes https://github.com/bazelbuild/rules_python/issues/2489
14 files changed
tree: dbe31ce23945f6830c16e72779b87dc4d3f78ca1
  1. .bazelci/
  2. .bcr/
  3. .ci/
  4. .github/
  5. docs/
  6. examples/
  7. gazelle/
  8. private/
  9. python/
  10. sphinxdocs/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazelignore
  15. .bazelrc
  16. .bazelversion
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .pre-commit-config.yaml
  21. .readthedocs.yml
  22. addlicense.sh
  23. AUTHORS
  24. BUILD.bazel
  25. BZLMOD_SUPPORT.md
  26. CHANGELOG.md
  27. CONTRIBUTING.md
  28. CONTRIBUTORS
  29. DEVELOPING.md
  30. internal_dev_deps.bzl
  31. internal_dev_setup.bzl
  32. LICENSE
  33. MODULE.bazel
  34. README.md
  35. version.bzl
  36. WORKSPACE
  37. 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.