Thomas Kluyver

Thanks everyone for the input. That looks to me like a rough consensus for option 2, where we keep the `flit` CLI without any drastic changes in its scope. I...

> I think the use VCS/not-use-VCS should be based on whether it is in VCS, not wether someone is using flit build or pipx run build. Sorry, but I'm not...

Sorry, I'm rejecting any solution where the backend has a VCS behaviour and a fallback behaviour. I can see how it 'should' make sense to distinguish things that way, but...

I'm waiting for [PEP 639](https://www.python.org/dev/peps/pep-0639/) before reworking the options for license metadata. The TODO comment in that code explains why it doesn't put the license from `pyproject.toml` into the current...

But it might need to be a comma separated list after all: https://mail.python.org/archives/list/[email protected]/thread/LFTLGMIIB5PRG7NUUIGGGX4COGX53DMR/

I'm open to thinking about ways to make it easier to manage version numbers. But the sort of solutions people have proposed so far all involve extra complexity inside every...

I'm not concerned about what it involves for the developer. I'm concerned about what the package winds up doing at runtime. It needs some extra dependency installed, and then it...

I've been thinking again about how to incorporate something like setuptools_scm, and I'm afraid I still don't see a good option. I can see the attraction of getting the version...

Flit doesn't support projects with build steps (see #119). Not even optionally, not even if you want to supply all the logic of the build step yourself. Flit is built...

It's sort of expected, because `flit install` builds a wheel and then asks pip to install it. But it probably shouldn't be. Does it exclude the file if you do...