tree f65eea8dbd90529aaf9e99e41b7a3517f391849f
parent ab0cc82b343ad93736ea4094844839a717190fd8
author Serge Bazanski <serge@nexantic.com> 1581411741 +0100
committer Serge Bazanski <serge@nexantic.com> 1581411741 +0100

Explicitly provide Python toolchain, provide `python` in build container

This fixes being able to run py_binary targets within the build
container.

Each py_binary creates a stub that always has the #!/usr/bin/env python
shebang, and as such we need to have `python` available in the build
container. The stub then dispatches into the right Python interpreter,
which we now configure explicitely via rules_python's py_runtime_pair.

Test Plan: nothing breaks, future uses of py_binary (eg D389) will make actual use of this

X-Origin-Diff: phab/D390
GitOrigin-RevId: 78b6c51f09c720a46fbe2e6cbadb2a97d1161f7b