-
-
Notifications
You must be signed in to change notification settings - Fork 1k
-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
virtualenv will pick up a [install] settings in setup.cfg for installing pip #740
Comments
I've run into this issue as well. Is there a workaround? |
hit by the same issue, and in the created virtualenv trying to |
Just had an hour of head-scratching over this. To make matters worse, I had the |
This issue also causes problems if
I encountered this issue in tox-dev/tox-venv#25 when invoking |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just add a comment if you want to keep it open. Thank you for your contributions. |
This still occurs. |
Just hit this as well. Would be useful if we could at least pass a flag or something to virtualenv to ignore it. I think we're likely just going to end up doing a |
Does pip have a flag to ignore it's config files? |
Fixed with #1641 on python 2 👍 |
I happened to have a setup.cfg in a directory that I've installed a virtualenv from (ie. the cwd contained the setup.cfg). To my surprise, virtualenv picked up on the [install] section and wanted to install pip into the prefix mentioned there.
Testcase:
The text was updated successfully, but these errors were encountered: