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

Configure install to use local projects #5032

Closed
mforkel opened this issue Feb 17, 2018 · 8 comments
Closed

Configure install to use local projects #5032

mforkel opened this issue Feb 17, 2018 · 8 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@mforkel
Copy link

mforkel commented Feb 17, 2018

  • Pip version: 9.0.1
  • Python version: 2.7.14
  • Operating system: Ubuntu 17.10

Description:

I'm using local projects, i.e. non-VCS "editable" installs, in virtual environments during development.

There does not seem to be an option similar to --find-links for configuring pip install to use those local projects to fulfill requirements. I think there are at least two use cases:

  • Overriding distributions with local development versions and
  • fulfilling recursive requirements of local projects during install.
@pradyunsg
Copy link
Member

@mforkel What are you trying to achieve here? It's unclear from the description to me.

@pradyunsg pradyunsg added the S: awaiting response Waiting for a response/more information label May 10, 2018
@mforkel
Copy link
Author

mforkel commented May 10, 2018

Thanks for looking a my issue.

I'm working on multiple interdependent Python packages in parallel. During development, I would like to be able to specify in pip.conf (or on the command line, for that matter) where these packages can be found - basically a path of the directory containing setup.py. That would allow me to create a virtual environment, pip install -e one of my packages and have pip fulfill some of its requirements by creating editable installs for some of the other packages in development. Note that I don't want to perform a snapshot and install a clone captured in an archive.

The packages specified as local editable installs should overide packages available from (local) PyPI-like repositories, depending on the development and the archiv version..

This is related to #5031.

@pradyunsg
Copy link
Member

Is there some reason you can't specify the packages in a requirements.txt and install them?

@mforkel
Copy link
Author

mforkel commented May 10, 2018

I don't want to install all packages I'm working on in each virtual environment. I would like pip to know where to find packages under development, so I can install one of them and have pip resolve its requirements, using development versions where available (and appropriate, depending on the version numbers). The requirements should only be listed int the setup files.

@pfmoore
Copy link
Member

pfmoore commented May 10, 2018

This sounds like a pretty specialised situation, and as far as I can tell from your description, it would be quite complex to implement. I'm inclined to say that it's not sufficiently general to be something we'd want to add code specifically to support.

If you can more precisely specify what changes you'd like to see in pip, and provide some indication that the workflows that these changes would enable would benefit enough pip users to warrant the changes (i.e. it's not just you that works like this :-)) then we can reconsider the proposal.

@pradyunsg pradyunsg added the S: needs triage Issues/PRs that need to be triaged label May 11, 2018
@pradyunsg pradyunsg removed the S: awaiting response Waiting for a response/more information label Jun 23, 2018
@pradyunsg
Copy link
Member

+1 to what @pfmoore said. @mforkel Ping?

@pradyunsg pradyunsg added the S: awaiting response Waiting for a response/more information label Jun 23, 2018
@xavfernandez
Copy link
Member

Closing due to lack of response.

@lock
Copy link

lock bot commented May 31, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label May 31, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 31, 2019
@triage-new-issues triage-new-issues bot removed the S: needs triage Issues/PRs that need to be triaged label May 31, 2019
@pradyunsg pradyunsg removed the S: awaiting response Waiting for a response/more information label Mar 17, 2023
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