-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use python3 on macOS #15045
Use python3 on macOS #15045
Conversation
@bazel-io fork 5.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested a case where the python script is run and this works, the script does not need updates. I didn't catch this in previous testing because we don't have any libraries that hit the slow path of libtool.sh
Our teams needed additional changes to unblock us: ButterflyNetwork@938c427 We're still on 4.2.2, so that's the base of that commit. We only tested these changes on macOS. Edit: did more digging and found our changes were already made in #11201. Would be great to get them ported back to 4.x. Any plans to do that? If someone can point me in the right direction (e.g. the right base branch, commit format, etc.), I could stage a PR to do so. |
@googlewalt asks:
|
I tested and did not have to set that, without knowing more about the error I'm not sure what conditions that shows up in to repro |
macOS 12.3 removed `/usr/bin/python2.7` and `/usr/bin/python`. We need to use `python3` now. Closes bazelbuild#15045. PiperOrigin-RevId: 436548693 (cherry picked from commit 3785677)
macOS 12.3 removed `/usr/bin/python2.7` and `/usr/bin/python`. We need to use `python3` now. Closes #15045. PiperOrigin-RevId: 436548693 (cherry picked from commit 3785677) Co-authored-by: Oscar Bonilla <[email protected]>
macOS 12.3 removed
/usr/bin/python2.7
and/usr/bin/python
. We need to usepython3
now.