-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Changed behavior with --extra-index-url with pip 9 #4195
Comments
Hello? Any response? Hit this again today which reminded me of the problem at hand. |
Interestingly enough, this is an issue with virtualenv. The pip it installs is just broken by default. Downgrading to pip 8 and then upgrading back to pip 9 fixes it. Virtualenv version is: |
Just hit this exact same issue (private repo, pip install fails saying it cant find the package). We followed the exact same procedure (downgrade to ~8, upgrade back to 9) and it worked. We are all shaking our heads at this. |
Are you using virtualenv that came with Debian? They patch the pip they install with that and the upgrade/downgrade dance ends up forcing you to use the unpatched version from PyPI. It could be an issue with the patching done by Debian. |
This is definitely a bug in the debian patch for pip ; it was reported here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837764 a long time ago but went dead. It is still happening today. |
I don't actually think this is completely a downstream bug. The issue is related to how debian unvendors vendored libs, but we trip over that because the exception is pip._vendor.requests.exceptions.HTTPError not pip._vendor.requests.HTTPError. I'll get a PR up shortly that seems to fix this for debian (and also happens to be more like the other exception handling in index.py). |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description:
We have a private internal package we use for our projects that is hosted on our own internal server. That packaging server only has our private packages and is not a full PyPI mirror, because it's not what we need. In the past, I have been able to run:
and it works fine. However, now when I run this command, I get an error from pip saying it can't find a specific package on
pip.croscon.com
. This package is not our internal package and is one we normally pull from PyPI. This critically errors and fails. Going back to pip 8 fixed this.What I've run:
The text was updated successfully, but these errors were encountered: