Skip to content
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

`--install-option` should work for wheels? #1716

qwcode opened this Issue Apr 13, 2014 · 3 comments


None yet
3 participants
Copy link

commented Apr 13, 2014

currently, for installing wheels:

  • --user & --root works
  • pip's own --target works, (but this is often not very useful, since it only installs modules)
  • --install-* options work if set in distutils config files (since wheel installs, in pip, ultimately get their scheme from distutils internally)
  • pip install --install-option= does not work

I understand there's a desire for wheel to work in the future with no connection to distutils at all, but at the moment, the situation is fractured, and not ideal at all to have less control than sdists when installing.

for now, it seems to me, we should do the work to map the --install-option params into pip.locations.distutils_scheme a la this comment #1439 (comment)

failing that, I think we do one of the following:

  • fail when wheels are found and using --install-option
  • although I would hate doing it "quietly", automatically map to --no-use-wheel when using --install-option

This comment has been minimized.

Copy link

commented Jul 18, 2014

Just ran into this, trying to get to install the pip binaries in /usr/bin rather than /usr/local/bin. Unfortunately because setuptools is needed to install from source, the --no-use-wheel isn't an option until it's too late.

The use case in this instance is installing pip for python3 on a ubuntu system that already has a pip binary placed there by a deb package.

This existing pip binary is in /usr/bin, however installs a binary in /usr/local/bin since there's no conflict there, which is then prefered over the existing python2 pip. The new pip binary is only created when there's no conflict, so forcing it to install into /usr/bin would solve this issue as only a new pip3 binary would be created.

EDIT: To clarify, the desired option here was --install-scripts


This comment has been minimized.

Copy link

commented Oct 16, 2014

+1 on having a --install-scripts option for wheel installations.
After all wheels are supposed to make life easier for end-users, but on MacOS, for which wheels are really great otherwise, users very rarely have the default location for Python scripts in their path.
So you have to either tell people to add it to PATH or to create a symlink and, simple as this may seem, it's not a one-line installation anymore and already scares some people.
If you could tell them instead to use:
pip3 install package --install-scripts /usr/local/bin
it's quite a bit better already


This comment has been minimized.

Copy link
Contributor Author

commented Apr 13, 2015

closing as dupe to #2677

@qwcode qwcode closed this Apr 13, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.