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.
Determine what should be done about --(install|global)-option with Wheels
See original GitHub issueCurrently pip has --install-option and --global-option to make it possible to pass flags to the setup.py invocation. However these currently get ignored completely when installing from Wheel. This previously wasn’t a big deal because commonly these options are only used for compiled packages and those often don’t have Wheels on the platforms you might need these options on. However now in pip 7.0 via #2618 we now attempt to automatically build wheels for all projects. This means that, assuming we can build a wheel, these options are just completely ignored.
So what do we do with these options? Do we make their use imply --no-use-wheel? Do we attempt to convert them? Get rid of them?
Issue Analytics
- State:
- Created 8 years ago
- Reactions:6
- Comments:36 (24 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
+1 to
--install-scriptsfor wheelsI too have now ran into this (or at least something similar).
I need ‘wheel install-scripts’ to be able to install to a custom path. Right now, it zonks the script wrapper always in ‘/usr/bin’ without the ability to change the prefix path.
Is there really no way to have console scripts post wheel install to a custom path? I can certainly do this with eggs.