-
Notifications
You must be signed in to change notification settings - Fork 97
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
[Self-filed] Switch back to rules_python when their issues are fixed #168
Comments
cpsauer
added a commit
that referenced
this issue
Feb 1, 2024
Mostly reverts 0e5b1aa Tracking restoration at #168 Please see - #163 - bazelbuild/rules_python#1732 - #165 - (rules_python issue to come) - #166 - bazelbuild/rules_python#1169
[Intentional blank comment, added to make it clear from the table view that this isn't a user issue lacking a response.] |
cpsauer
added a commit
that referenced
this issue
Feb 1, 2024
This was referenced Feb 1, 2024
Closed
Closed
Blocks #148 |
This was referenced Feb 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We'd switched to rules_python to get a hermetic python interpreter and to be able to make sure that everyone was on the same python version, rather than relying on system python. However, a number of issues caused us to revert for now.
Please see
rules_python
bazelbuild/rules_python#1169The text was updated successfully, but these errors were encountered: