Filipe Laíns 🇵🇸

Yes, we'd have to give it a different key, but keeping the same semantics. sdists are exactly the reason why. Build and sdist dependencies are different, while we could try...

Implementing this is possible, but the commitment to use the metadata from the `prepare_metadata_for_build_wheel` hook is annoying, and makes things a bit more complicated. Actually, we could consider simply checking...

To be clear, this **can** be implemented, and would be a nice improvement, just not really high-priority right now, so I am re-opening. The specific workflow issue mentioned is solved...

Fetching the metadata for the package. See https://pypa-build.readthedocs.io/en/stable/api.html#build.util.project_wheel_metadata, and https://github.com/jaraco/jaraco.packaging as an example use-case. This is especially relevant in our build backend because we are mainly target compiled, often big...

No, I mean look at what that project does, not the build backend it uses. It fetches the metadata and injects some of the fields in sphinx. > This new...

@di could you advise on the correct path forward?

I have reopened that issue :+1:

Not really, if I have an install directory, we'd have to run `meson install` to use it. That can be problematic as it is very tricky for us to inject...

No, the editable wheel would include symlinks to the build directory or source tree, depending if the file is generated or not. The current approach for normal wheels is to...

> What I had expected was writing directly a separate directory of symlinks, and then use a `.pth` file or another mechanism to point to that directory. That would be...