When running under bazel, Emsdk should use the bazel python through something like py_binary instead of the system python

[logankaser]

It seems like the bazel wrapper escapes the bazel sandbox and relies on having the correct version of python installed on the system. Is there a way to force it to use the bazel python tool chain?

[allsey87]

It seems like the bazel wrapper escapes the bazel sandbox

Could you go into a bit more detail here? What sort of issues has this caused you? Referring to #1422, I am just using the native implementation of py_binary (not the one from rules_python) which I suspect still uses the system installed Python.

If I get time to work on #1422, I intend to switch it over to python_rules since that might work around bazelbuild/bazel#17629.

[logankaser]

It seems like the bazel wrapper escapes the bazel sandbox

Could you go into a bit more detail here? What sort of issues has this caused you? Referring to #1422, I am just using the native implementation of py_binary (not the one from rules_python) which I suspect still uses the system installed Python.

If I get time to work on #1422, I intend to switch it over to python_rules since that might work around bazelbuild/bazel#17629.

For example, https://github.com/emscripten-core/emsdk/blob/ce1d281ce65b5c7398b17ed6484efc6a3901df6f/bazel/emscripten_toolchain/emcc.sh
just invokes system python3.

[allsey87]

For example, https://github.com/emscripten-core/emsdk/blob/ce1d281ce65b5c7398b17ed6484efc6a3901df6f/bazel/emscripten_toolchain/emcc.sh
just invokes system python3.

Indeed it does, I am not sure what I was on about in my previous comment.

[phlax]

yeah - would be great to fix emcc.sh - we patch it out to make it use hermetic python - perhaps we can upstream the patch