Any public interface should not be marked incompatible, since the @system_python repository is specific to *this* workspace. Downstream users can name it whatever they want or use a hermetic python build, in which case this repository won't be defined.
PiperOrigin-RevId: 492103118
The current behavior will crash any Bazel command immediately, due to our declared pip dependencies in WORKSPACE, if python3 can't be found. The new behavior will mock out these workspace dependencies and allow any non-python targets to run. Python targets will be skipped by wildcard expressions if there's no system python3, and will fail when run directly, due to compatibility mismatch.
PiperOrigin-RevId: 492085254
Adam Cozzette
Protobuf Team Bot
Richard Levasseur
Thomas Van Lenten
Joshua Haberman
Mike Kruskal
Matt Kulukundis
Joshua Haberman