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.

Sign up for GitHub

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

Jump to bottom

Dont force setup of `@pip3` in bazel workspace #863

Open

phlax opened this issue Oct 19, 2023 · 1 comment

Member

phlax commented Oct 19, 2023

Probably we can use label_flags etc to define where the deps come from and remove the need to set this up

Member Author

phlax commented Oct 19, 2023

cc @ravenblackx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment