Thomas Kluyver

Hi @flying-sheep, sorry it's taken me ages to look at these PRs (this and #374). I know I'm rather neglecting my role as a maintainer of Flit - when I...

Similar to https://github.com/pypa/pip/issues/6100, it looks like pip & pep517 are hiding the real error details of what went wrong here.

Yup, you're right that `flit build` does something a bit different from the PEP 517 hook. And this is definitely a bit awkward. A brief bit of history: The first...

I haven't, and probably won't, hardcoded any default exclusions. There might be useful clues about how the project is built or tested in something like a CI workflow definition, and...

You can specify a Python version like `requires-python = "~=3.8"` in `pyproject.toml`. Flit doesn't and isn't likely to support restricting based on the architecture Python is compiled for, because it's...

Yup, it's quite conceivable that some of this stuff might be easier with conda. Although looking at the pytorch installation instructions, it seems to be doing something similar - `-c`...

I think warning makes sense at least. I think I tried to start a discussion when the PEP was being discussed about whether backends should actually *error* on unexpected keys,...

The 'improperly specified' thing almost seems tautological. OK, we'll raise an error if it's wrong, but is an extra key wrong? Might the spec be extended in the future? And...

OK, who wants to do a PR? :slightly_smiling_face:

Yes, Flit should check that. It's a quirk because in the old style metadata (`[tool.flit.metadata]`), you specified the import name first, which has to be a valid Python identifier, and...