--global-option for a specific requirement in requirements file disables use of wheels globally

[fillest]

• Pip version: 7.1.2 (tested with 9.0.1 with the same result)
• Python version: 2.7.6
• Operating System: Ubuntu 14.04

Description:

We have a big requirements file and use wheels. Now we've added a new package and need to pass some build arguments to it. I've figured out it can be placed into requirements file this way:

confluent-kafka==0.9.2 --global-option=build_ext --global-option="--rpath=/opt/librdkafka/lib/"

Pip is invoked like this:

/home/x/venv/bin/pip --disable-pip-version-check --cache-dir ~/pipcache wheel --build /tmp/pipbuild_x --src /tmp/pipsrc_x --find-links ~/pip_wheels_x -i https://our-pip-index-using-devpi --wheel-dir ~/pip_wheels_x --requirement deploy/requirements/all.txt

This message is printed:

/home/x/venv/local/lib/python2.7/site-packages/pip/req/req_file.py:129: UserWarning: Disabling all use of wheels due to the use of --build-options / --global-options / --install-options.
   cmdoptions.check_install_build_global(options, opts)

I expected it to use wheels for other packages but it stopped to use wheels for all the packages mentioned in deploy/requirements/all.txt. This breaks the installation process for us, because we use some private wheel-only packages uploaded to our devpi transparent index mirror.

Is it intended (why then?) or per-requirement handling is not implemented yet?

(Also after upgrading pip to 9.0.1 and reverting pip version back to 7.1.2 in our requirements file I got Could not find a version that satisfies the requirement pip==7.1.2 (from -r deploy/requirements/pip.txt (line 1)) (from versions: ) but this one may be a devpi issue, not sure yet)

[pradyunsg]

Hey @fillest! Thanks for filing this issue and sorry for the lack of a response all this while.

Could someone try reproducing this on the current master, with a small test case? I'm not sure why this is this way. Looking at the code, I don't see any hints as to why it was done. My suggestion would be to split up the requirements to install all the wheel-only dependencies in a separate pip run from one using --global-option.

Thanks and sorry again for the wait.

[iwanb]

I have the same issue with pip 10.0.1.

It can be reproduced if you have a package which fails to install if it is not from a wheel, e.g. because of missing include files. For example with lxml, on CentOS I do not have libxml2-devel installed, so if I have the requirement:

lxml
other --install-option="--my-option"

It fails to compile lxml, while it works without the --install-option on the other package.

[iwanb]

Is there any update on this?

I created a functional test for it and attempted a fix in this commit:
iwanb@6ead47f

I am not familiar with the code so if somebody could have a look at it :)

[chrahunt]

Related to #2677, where I think the motivation for the current behavior is indicated.