8 ms·
Ah interesting, thanks for that! I was frustrated once again recently to note that `pip install --dry-run` required me to pre-download all packages, so I assume
by mikepurvis 1y ago
Ah interesting, thanks for that! I was frustrated once again recently to note that `pip install --dry-run` required me to pre-download all packages, so I assumed nothing had changed.
- zahlman 1y agoYou could do worse than to start using --only-binary=:all: by default. (It's even been proposed as default behaviour: https://github.com/pypa/pip/issues/9140 https://github.com/pypa/pip/issues/9140) Even if you can't actually install that way, it will point out the places where sdists are needed. In principle, separate metadata availability should still at least be possible for most sdists eventually. But I'm not the one calling the shots here.
- mikepurvis 1y agoFor clarity, if I do pip install -r requirements.txt --dry-run --only-binary=:all:` Should I expect that to download only metadata and not whole wheels/sdists for everything? Or does that depend on everything in my requirements file being available as a wheel?
- zahlman 1y agoIf there are things not available as a wheel, it should just fail (and highlight what failed).