Skip to content
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

Open
cpsauer opened this issue Feb 1, 2024 · 2 comments
Open

Comments

@cpsauer
Copy link
Contributor

cpsauer commented Feb 1, 2024

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

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
@cpsauer
Copy link
Contributor Author

cpsauer commented Feb 1, 2024

[Intentional blank comment, added to make it clear from the table view that this isn't a user issue lacking a response.]

@cpsauer
Copy link
Contributor Author

cpsauer commented Feb 1, 2024

Blocks #148

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant