Filipe Laíns 🇵🇸
Filipe Laíns 🇵🇸
No changes from CPython's side are required to fix this, and nothing significant will happen there until 3.14 at least anyway.
No, not yet unfortunately, but shouldn't users be using a Spack-provided Python?
PEP 517 is backwards compatible, it should work on legacy packages, the opposite is the issue, pip trying to use the legacy path for packages that need PEP 517.
Yes, I think this is a good idea.
Hi @peter-urban, thank you for raising this issue. I think this use-case could be meet by allowing users to specify Meson options, which is something we do want to do,...
I am not sure what to say, the `meson` script *should* be there, as meson is a dependency. `pip install --user .` not working on certain scenarios is a major...
> This seems fine to me as a fix for `meson-python`, since it has a hard dependency on `meson` so it should always be installed in the Python environment in...
I think it would be beneficial for you to describe your dev environment setup. Other thought, have you updated your pip? This can happen when building without isolation if the...
Oh, that makes sense, thank you for posting that output! This is another issue cause by Debian's patching of Python. As a workaround, we can try to add that missing...