Investigate workaround for OSX Monterey & Bazel 4.2.x python env not found issue
dennycd opened this issue · 0 comments
dennycd commented
OSX Monterey removes python2 in default system path, and as a result, causing bazel 4.2.x iOS target build failure due to "python" not found error. Upgrading to bazel 5.x appears fixing the issue. However, this is dependent on gRPC c-core's bazel version upgrade
Investigate possible workaround with using bazel 4.2.1 on Mac OSX Monterey for iOS bazel tests.
related PR discussion grpc/grpc#29599