Lennart Regebro

I see. Well, I guess that it might be possible to implements something like this in some future major rewrite.

My thinking looks something like this: Pyroma 4 will: * Support PEP517 * Use `build.prepare()` to get metadata * Deprecate the old setuptools hack it used before. Pyroma 5 will...

Ah, yes, that makes sense. I'll fix that for beta 2. Do you have an example package this happens on that I can double check on?

It is correct, but also not. :-D I released 4.0b2, it should fix this.

Well, the tooling isn't much work, but yes, if you make a PR then I'll add it to 4.x.

Looks good, thanks!

IIRC reading metadata from pyproject.toml isn't supported yet.

OK, great! I remember I was waiting for a release of setuptools, I didn't expect it would just start working by itself, but it seems it did, then. > i.e....

Reopened this as that PR only implemented PEP517 support, and not PEP621, so I don't know if it enough for poetry support. But beta 4.0b1 is out.

Having three copies to update at the same time does put a lot more pressure on the PC. But I think it's important that the transitions happen in sync. When...