fix: use `exec` to invoke the stage-2 bootstrap for non-zip case (#2047)

When the two-stage bootstrap is used, the parent shell process runs
python as a child
process, which changes how signals are propagated. Specifically, if a
signal is sent
_directly_ to the parent (e.g. `kill $parent`), the child process
(python) won't receive
it and it will appear to be ignored. This is because the parent process
is busy waiting
for the child process.

To fix, invoke the python process using `exec` instead. Because the
process is entirely
replaced, signals are sent directly to the replacement. This can't be
used for zip files,
though, because they rely on a catching the exit signal to perform
cleanup of the extracted
files.

Fixes https://github.com/bazelbuild/rules_python/issues/2043

---------

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