feat: provide access to arbitrary interpreters by philsc · Pull Request #2507 · bazel-contrib/rules_python

and others added 10 commits

October 29, 2024 21:05
Run a specific interpreter:
* `bazel run @rules_python//tools/run --@rules_python//python/config_settings:python_version=3.12`

Run interpreter from a binary:
* `bazel run @rules_python//tools/run --@rules_python//tools/run:bin=//my:binary`
    $ bazel run //python/bin:repl
    $ bazel run //python/bin:repl --//python/bin:repl_dep=//python/runfiles

philsc

aignas

rickeylev

@philsc

@philsc

@philsc

@philsc

@philsc

@philsc

@philsc

@philsc

@philsc

@philsc

@philsc

@philsc

@philsc

@philsc

I noticed that my `$(location //path/to:target)` wasn't getting
expanded when writing a test. This patch fixes the issue by forwarding
the already-expanded environment from the inner target to the outer
target.

@philsc

@philsc

@philsc

@philsc

philsc

aignas

rickeylev

rickeylev

@rickeylev

Merged via the queue into bazel-contrib:main with commit 34e82cd

Feb 16, 2025

3 of 4 checks passed

github-merge-queue bot pushed a commit that referenced this pull request

Feb 17, 2025
This was a forgotten part of the original PR (#2507) implementing it.