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

pip wheel -r doesn't build wheels for dependencies of editable requirements #1775

Closed
Symmetric opened this issue Apr 28, 2014 · 6 comments
Closed
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@Symmetric
Copy link

echo '-e ./module' | pip wheel -r /dev/stdin

Gives the output:

ignoring file:///home/me/module
You must give at least one requirement to wheel (see "pip help wheel")

The behaviour I would expect is for pip to create wheels for the dependencies of 'module', and skip making the wheel for 'module' itself (since it's an editable/develop module). If you don't want to install the dependencies, it seems that's what the '--no-deps' flag is for.

The use-case is an app where the components are all installed as develop/editable installs (using '-e ./module' in requirements.txt). For pip install -r requirements.txt this correctly fetches dependencies.

@qwcode
Copy link
Contributor

qwcode commented Apr 29, 2014

agreed, but moreover maybe pip wheel should just build the wheel for the editable requirement as well.

@qwcode
Copy link
Contributor

qwcode commented Apr 29, 2014

on 2nd thought, that will often end up with a confusing result.
working on a PR now though for the original problem.

@Symmetric
Copy link
Author

Awesome, thanks for the speedy response!

@Symmetric
Copy link
Author

After attempting to work around this issue, I've found a related problem with pip wheel handling of editable installs, which might factor in to your fix here.

If I have nested projects, with a dependency from the container to the contained project:

setup.py
/subproject/setup.py

requirements.txt:
  -e subproject

The wheel install fails, because it can't locate the dependency for subproject:

Could not find any downloads that satisfy the requirement subproject (from project==0.1)

I suppose this is to be expected, since per the above bug, the -e subproject line is being ignored. Not sure if this was on your radar already; I'm happy to provide more detail if you need it.

@Ivoz
Copy link
Contributor

Ivoz commented May 1, 2014

@Symmetric the name requirements.txt is simply a convention, not a standard; so pip / setuptools have never been designed to automatically find a project or projects using it. You can't use it for specifying dependencies like that.

it should probably work if you have in the top project a requirements.txt with

-e subsubject/
-e .

and then use pip wheel -r requirements.txt on that.

@ithinkmfallin
Copy link

I didn't get it? what is requirement.txt?
I am finding same problem on windows.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 4, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

4 participants