Cannot run Bazel without /usr/bin/python, even if /usr/bin/python3 exists

[ted-xie]

ATTENTION! Please read and follow:

• if this is a question about how to build / test / query / deploy using Bazel, or a discussion starter, send it to [email protected]
• if this is a bug or feature request, fill the form below as best as you can.

Description of the problem / feature request:

Bazel relies on /usr/env/bin python, which no longer exists in the newest update to my operating system.

Feature requests: what underlying problem are you trying to solve with this feature?

N/A.

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Remove /usr/bin/python symlink and run literally any Bazel workload.

What operating system are you running Bazel on?

Proprietary OS vaguely similar to Ubuntu 20.04.

What's the output of bazel info release?

INFO: Invocation ID: f21f4240-c757-4848-ac49-2acef7ed1685
release 4.0.0

If bazel info release returns "development version" or "(@Non-Git)", tell us how you built Bazel.

N/A

What's the output of git remote get-url origin ; git rev-parse master ; git rev-parse HEAD ?

N/A, using pre-built binary.

Have you found anything relevant by searching the web?

Looks like #8665 was never truly fixed Bazel-side. Users should not have to create system-level symlinks to run Bazel.

Any other information, logs, or outputs that you want to share?

N/A.

[keith]

This is a dup of #8685

[ted-xie]

I acknowledge that but there has been little/no traction on that bug. I was hoping to revive the discussion/raise the visibility of this issue by filing a new bug.

[philwo]

Hey @ted-xie, I'm sorry that this still isn't fixed. We'll get to it hopefully soon.

[lberki]

It looks like this is fixed by #13414 ?

[philwo]

@lberki Indeed! This looks like it might be an elegant fix for this :)

[sventiffe]

@philwo #13414 however stalled a while ago. Is anything preventing us from moving on? Would that PR also be included in a future 4.x update?

[philwo]

We need to merge that PR, I think it's the best fix we have.

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

[github-actions]

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!