Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
~/.pip/pip.conf and virtualenv conflict
See original GitHub issueI couldn’t find this issue documented anywhere, but if you specify install-option in ~/.pip/pip.conf, it is not overriden by virtualenv. I specify --prefix=/path/to/somwhere in install-option due to user restrictions on my work pc, and with it set, any installs in a venv (with $PIP_RESPECT_VIRTUALENV enabled) still install in the path specified by install-option. This was not an expected behavior for me, but I’m not sure if ignoring pip.conf is the correct course of action either. Perhaps documenting such behavior is best. Another odd thing is that you then cannot uninstall while in the virtualenv, as the package is not installed in the venv, and pip cannot find it.
This happened to me when using pip 1.4.1 and 1.5.6 and virtualenv 1.11.6.
Issue Analytics
- State:
- Created 9 years ago
- Reactions:2
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
My current fix is to set
$PIP_CONFIG_FILEto/dev/nullviavirtualenvwrapper’spostactivatehook and unsetting it inpostdeactivate.Can someone please provide clear instructions on how to reproduce this?