Better error message for editable installs with missing --no-build-isolation #512
Comments
This is not strictly true. It is required only when
The stack trace you obtain most likely is informing you that
Meson definitely cannot do it. meson-python is the component that sits between the build front-end (most likely pip) receiving the We could issue a warning if we detect that I think that using build isolation for editable wheels is a misfeature of build front-ends. |
That does seem reasonable to me. It's likely (but not certain) that this was user error and rebuilds are going to break.
Perhaps indeed. However, the users here are typically more advanced, and may actually pay attention to such warnings. The warning must be visible without the with
Agreed. It's unlikely to change unfortunately. |
AFAIK, this is not something we can control. I don't think emitting a warning that no one is going to see is very useful. |
|
The only option that remains is to return an error if |
|
That does sound right - and erroring out there does allow us to clearly explain the problem to the user. |
|
Thanks for the explanations. In case it helps, I provide the exact case that triggered me opening this issue. In the example in matplotlib/matplotlib#27005 the build runs without error. The stacktrace happens during import of the library at runtime: The mentioned If one cannot detect the/all issues during the build, that's ok. But turning the above runtime exception into a useful message would be a big help. |
|
This is the kind of error that is not possible to detect at wheel build time. The package is failing to compile and the exception is telling you just that: the |
Meson needs the
--no-build-isolationflag for editable installs. I've stumbled over a missing--no-build-isolationflag multiple times when a project adopted meson but I followed old install instructions.This results in a quite cryptic stack trace. Could meson detect an editable install with missing
--no-build-isolationand issue a more informative warning?The text was updated successfully, but these errors were encountered: