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
Error installing Bottleneck 1.2.0 from behind proxy #158
Comments
A small change to how numpy is handled was made after the 1.2.0 release. Could you test with the current master branch? |
Here's my updated
And here's the updated build log:
Pip doesn't seem to be properly using the proxy when cloning a git HTTPS repo. Not sure how I make it do that. I'll keep playing with it. |
Hm, just stumbled onto this issue, which has been open since 2011. That doesn't bode well.... |
How about changing the order of your requirements file? Would it help to put numpy before bottleneck? That might prevent bottleneck from trying to install numpy. |
In the short term, that would probably work. We have some automated scripts that spit out |
I'd like to reopen this issue. I finally spent the time to move NumPy to the top of the requirements file. Here's my current requirements file:
Here's the error that CI is throwing:
So even though NumPy is listed before Bottleneck, this doesn't fix the error. Downgrading Bottleneck to 1.1.0 fixes the problem. |
Sorry, I don't know why bottleneck doesn't see the numpy you installed. Your log says:
But it doesn't say anything about installing numpy. Does it get installed (and is available system wide) before bottleneck in downloaded? |
Excellent question. What is looks like is that running |
I just ran into an error where some unit tests are failing after upgrading from 1.1.0 to 1.2.0. This is on a work-hosted GitLab instance that's behind a proxy. Here's my virtual environment:
Here's the output of my CI output attempting to install 1.2.0:
And if I use 1.1.0, it succeeds:
It seems to be related to the way the NumPy requirement is handled in 1.2.0.
The text was updated successfully, but these errors were encountered: