commit ea80366b29219d3dad8c90191c21b77a4525875a
author Andrew Lindesay [Canva] <143454275+andponlin-canva@users.noreply.github.com> Mon Mar 17 16:30:18 2025 +1300
committer GitHub <noreply@github.com> Mon Mar 17 03:30:18 2025 +0000
tree 2eceef47754a03e2ccc8655044e44592b7dbbebe
parent 4079953a8397b22ee30c3a1534d04211c566959c

feat: env-var for additional interpreter args in bootstrap stage 1 (#2654)

There is no means to be able to provide additional interpreter arguments
to the `bash`-based stage 1 bootstrap system at launch time.

The Intelli-J / Bazel plugin typically launches a `py_*` rule build
product with something like this (abridged) using a Python interpreter
from the local environment;

```
python3 /path/to/pydev/pydevd.py --client 127.0.0.1 --port 12344 --file /path/to/built/python-file
```

When the `bash`-based bootstrap process is used, this mechanism not
longer works. This PR will mean that a potential future Intelli-j /
Bazel plugin version may be able to launch the build product differently
and inject additional interpreter arguments so that the debug system can
be stood up in this sort of a way;

```
RULES_PYTHON_ADDITIONAL_INTERPRETER_ARGS="/path/to/pydev/pydevd.py --client 127.0.0.1 --port 12344 --file" /path/to/bash-bootstrap-stage1-script
```

The work to support this in the Intelli-J / Bazel plugin has not been
done; it would have to be undertaken some time after this change were
available.

---------

Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com>
Co-authored-by: Richard Levasseur <rlevasseur@google.com>