-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Comments
Let's do it. Static build dirs have caused a lot of problems. |
well, I guess normally a deprecation includes an FYI on what the alternative is, but we don't have those yet E.g. for Given that, should we wait? |
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. |
If we wait, then it's 2 cycles before we can move to mkdtemp build dirs, because |
committed to 1.5.X 48f8c0a |
what's the correct way to check what's about to be installed without installing it then? |
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? |
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. |
@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.The text was updated successfully, but these errors were encountered: