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

Create venv for whole project, rather than individual targets #6

Open
mattem opened this issue Apr 14, 2022 · 0 comments
Open

Create venv for whole project, rather than individual targets #6

mattem opened this issue Apr 14, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@mattem
Copy link
Member

mattem commented Apr 14, 2022

Currently venv creation is tied to the terminal py_binary or py_test.

Under bazel this is fine and what we want, but for IDEs the user likely wants to create a venv for all the targets in their project, ie, all the test and binary targets in a given scope, or at the very least all the test targets so the IDE can run them.

This will lead to potential differences between testing under bazel and testing via the IDE as tests may have access to dependencies in the IDE that they wouldn't have under bazel.

@mattem mattem added the enhancement New feature or request label Feb 14, 2023
@alexeagle alexeagle added this to the 1.0 milestone Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants