Xavier Fernandez

I'd rather not have a "manylinux" specific option. Maybe a more general option `--only-pure-python` or something akin to `--no-binary` or `--only-binary`...

@pfmoore it adds a manylinux flavor to the `arch` in addition to the supported vanilla `arch`. We could maybe piggyback on #3760 and allow `--platform` option for `pip install`.

FWIW I agree with Pradyun that our PEP 517 implementation should first be improved (#7294 & #9081 are great examples) before making it the default.

> All that would involve would saying something like "Cannot build wheel for legacy install, please install the wheel project or switch to `pyproject.toml`". > And converting that to a...

Fair points but I suspect we'll then also get users asking "why does pip complain that wheel is not installed and does not install it already ?" ^^ It seems...

> @xavfernandez I'm somewhat confused. The original proposal here was essentially "if we get through the build code paths, and end up at the point where we currently do setup.py...

> The second "otherwise" doesn't seem like it would ever happen? Or was that meant to be "otherwise (if there's no pyproject.toml and no setup.py)"? You're right. Someone must have...

Since optparse is deprecated it would make sense to switch to argparse. But I think @dstufft was planning to switch to click.

A release with python 3 support would indeed be nice :)

Actually, I'd say PEP-508 went too far on the other side (allowing PEP-440 comparisons for everything that looks like a version): cf discussion https://github.com/pypa/packaging/pull/101#pullrequestreview-32037512