Bazel 0.27.0

[Profpatsch]

I commented out the src deps for now. See commit.

bazel now uses python3 by default, and it didn’t build without adding python3 to the custom bash. I’m not sure this is the right thing to do. cc @mboes

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Assured whether relevant documentation is up to date
• Fits CONTRIBUTING.md.

---

cc @kalbasit @groodt

[kalbasit]

I commented out the src deps for now. See commit.

I think that's fine given that we had to disable them in Bazel 0.26 anyway. Should we just remove the code, for now, to keep the derivation clean? We can file a separate PR with all of it re-enabled so we have something to start working on?

bazel now uses python3 by default, and it didn’t build without adding python3 to the custom bash. I’m not sure this is the right thing to do. cc @mboes

I think that this is fine as well. Last time I spoke to the Bazel team, they informed me that Python 3 is going to become the default Python interpreter for Bazel internals and possibly the default toolchain.

[kalbasit]

@GrahamcOfBorg build bazel bazel.tests

[marsam]

Shall we close this PR in favor of #63532?

[mboes]

bazel now uses python3 by default, and it didn’t build without adding python3 to the custom bash. I’m not sure this is the right thing to do.

Sounds fine.

[Profpatsch]

This will be integrated in the other PR.