@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.
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 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?
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 --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.
committed to 1.5.X https://github.com/pypa/pip/commit/48f8c0a18e931c60837b01e59e8fa3d16aa94fbf
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.
Most helpful comment
what's the correct way to check what's about to be installed without installing it then?