Daniele Nicolodi

I had a quick look and actually Meson includes a test case that does precisely this: a Cython extension module with a generated `.pxi` import. However, the test case does...

There are a few subtleties in compiling Cython. It would be nice to have a section in the documentation dedicated to Cython. Let's turn this issue into a documentation issue.

This is ready to merge when we are ready to bump the minimum required pyproject-metadata version.

As @eli-schwartz points out, `meson-python` is not responsible for defining where the components of a wheel package are installed. That is part of the `wheel` package format standard and ultimately...

I now see what you mean. However, I'm not convinced that prepending `share` to the data files location is the correct thing to do. For example, it would not make...

I'm very surprised that you were able to build the wheel that published on PyPI for CapyPDF 0.5.0. As the error message says, bundling shared libraries into wheels is not...

The way I would do this is to place the shared library next to the Python module and do not rely on the relocation of the shared library made by...

> Using 0.13.2 works. This is interesting. We must have tightened the check along the way. Unfortunately, the existing check is correct in the general case, thus relaxing it again...

> I tried this on macOS. With meson-python 0.13.2, the result is an `capypdf-0.7.0-py3-none-any.whl` and a wheel layout of: This is a bug in meson-python. meson-python should have detected that...

> Note the name is wrong, since the dylib is specific to macOS arm64 here This is an (obvious) oversight in meson-python. Fix in #526