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

autodetect virtualenvs instead of running collection inside them #2518

Closed
RonnyPfannschmidt opened this issue Jun 22, 2017 · 0 comments
Closed
Labels
good first issue easy issue that is friendly to new contributor status: help wanted developers would like help from experts on this topic type: enhancement new feature or API change, should be merged into features branch type: feature-branch new feature or API change, should be merged into features branch

Comments

@RonnyPfannschmidt
Copy link
Member

its a regular mistake of beginners to just put a virtualenv into a working directory, and then be puzzled that its indeed there and ready to ruin their day

we should detect it and warn about it instead

@RonnyPfannschmidt RonnyPfannschmidt added type: enhancement new feature or API change, should be merged into features branch type: feature-branch new feature or API change, should be merged into features branch good first issue easy issue that is friendly to new contributor status: help wanted developers would like help from experts on this topic labels Jun 22, 2017
@flub flub closed this as completed Jul 15, 2017
@nicoddemus nicoddemus added type: enhancement new feature or API change, should be merged into features branch and removed type: enhancement new feature or API change, should be merged into features branch labels Sep 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue easy issue that is friendly to new contributor status: help wanted developers would like help from experts on this topic type: enhancement new feature or API change, should be merged into features branch type: feature-branch new feature or API change, should be merged into features branch
Projects
None yet
Development

No branches or pull requests

3 participants