Paul Moore

Maybe we simply make `--prefer-binary` the default (rather than `--only-binary`)? I didn't suggest that originally because it means that we trigger "why don't I get the latest version?" questions. But...

> I think something like 98% of packages on PyPI have wheels in the latest release I'm pretty sure that's a figure I gave you, and I found the bug...

I think we could do a lot better if we could somehow identify which projects are "hard" to build from source. I feel like blocking sdists that build into universal...

I've got a big chunk of downloaded data from PyPI that I am querying to get a better feel for this sort of stuff. The biggest problem is the vast...

Most of what @mattip says looks right to me. For the final point, I agree that this needs a wider discussion than just the pip tracker, once we start going...

Let's focus back on the original proposal here. Do the @pypa/pip-committers as a group want to switch to `--only-binary :all:` being the default behaviour? If we do, @rgommers has offered...

PS One interesting piece of data on the whole issue of sdist building, would be to trawl through the tracker here and identify what proportion of our issues are related...

`pip download foo-1.0` could find a file `foo-1.0.tar.gz` which contained a project called bar, version 2.0. Pip has to get the package metadata (by building) to confirm that the filename...

It *is* a hypothetical edge case, that's the point. We're trying to standardise stuff so that people can't do stupid things like that, and we can assume everything's consistent, but...

> I can see how that could risk breaking pip install, but I still don't see how it's relevant to this issue? Mostly because there's so much shared code, that...