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

deprecate pip install --no-install / pip install --no-download #1345

Closed
qwcode opened this issue Nov 25, 2013 · 8 comments
Closed

deprecate pip install --no-install / pip install --no-download #1345

qwcode opened this issue Nov 25, 2013 · 8 comments
Labels
auto-locked Outdated issues that have been locked by automation kind: backwards incompatible Would be backward incompatible type: docs Documentation related
Milestone

Comments

@qwcode
Copy link
Contributor

qwcode commented Nov 25, 2013

@dstufft, if we want to move away from static build dirs to mkdtemp dirs, then best to formally deprecate pip install --no-install / pip install --no-download in v1.5, so we can do so (and moreover do all of #906) in v1.6 or later.

@dstufft
Copy link
Member

dstufft commented Nov 25, 2013

Let's do it. Static build dirs have caused a lot of problems.

@qwcode
Copy link
Contributor Author

qwcode commented Nov 25, 2013

well, I guess normally a deprecation includes an FYI on what the alternative is, but we don't have those yet

E.g. for pip install --no-install, the alternative will be pip unpack as mentioned in #906 (and the replacement for pip install --no-download will be pip install somepath\* , which is not documented atm, and may have bugs) .

Given that, should we wait?

@dstufft
Copy link
Member

dstufft commented Nov 25, 2013

We can wait if you think it's appropriate, however I'm not sure if there should be an alternative but I'll move that discussion over to the other ticket.

@qwcode
Copy link
Contributor Author

qwcode commented Nov 25, 2013

If we wait, then it's 2 cycles before we can move to mkdtemp build dirs, because --no-install / --no-download is what's blocking that. I'll go ahead and mark them as deprecated. I doubt many will notice or care that no alternative is mentioned atm.

@qwcode
Copy link
Contributor Author

qwcode commented Nov 25, 2013

committed to 1.5.X 48f8c0a

@abloch
Copy link

abloch commented Nov 13, 2018

what's the correct way to check what's about to be installed without installing it then?

@GreatBahram
Copy link

How do I get the list of package dependencies without installing it? it's a little bit weird to go for each package check it's a json. is there any better solution for this?

@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
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 kind: backwards incompatible Would be backward incompatible type: docs Documentation related
Projects
None yet
Development

No branches or pull requests

4 participants