Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

refactor --no-install/--no-download/--download (and use mkdtemp build dirs)

See original GitHub issue

pip install --download -> pip download pip install --no-install -> pip unpack pip install --no-download -> get rid of it (see comments from @g2p below)

along with this, move to mkdtemp build dirs (instead of static ones) in virtualenvs and global installs. I think the --no-install/–no-download “workflow” is what fueled the static build dirs pip has, which have caused so many problems.

Issue Analytics

State:
Created 10 years ago
Comments:62 (43 by maintainers)

Top GitHub Comments

7reactions

ssbarneacommented, Apr 1, 2016

Is there a way to emulate a --dry mode with current version of pip?

0reactions

meejahcommented, Jun 18, 2015

FWIW, I was using --no-download after doing a peep install of dependencies to ensure that a final pip install --no-download -e . didn’t go and download anything further (that won’t get verified, of course, because no peep). Now I’m giving pip a bogus proxy instead …