New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better support for Meson editable installs #2621
Comments
I think you could this:
...instead of There's also the |
I'm testing PDM for PyGObject, which is also meson-python based. I added [tool.pdm.options]
install = ["--no-isolation"] to |
Thanks for the advice. @amolenaar What about installation of the build dependencies? Do you also repeat them in a dev group? |
Yes, there's a dev group containing meson-python and friends. I linked the PR. |
PDM could be improved for packages using Meson and
meson-python
. Note that Meson is nowadays quite important. It is used in particular for Numpy, Scipy and Scikit-image.For these packages, the editable install (https://meson-python.readthedocs.io/en/latest/how-to-guides/editable-installs.html) has to be made with:
python -m pip install --no-build-isolation --editable .
and therefore the build dependencies have to be installed in the main virtual environment.
Currently, I have a
build
dev group:And I install with:
This is complicated and not optimal. PDM could detect that the project uses
mesonpy
, install the build requirements in the main env and install in editable mode with the correct option (--no-build-isolation
).Note that there is the same problem for subpackages in the repository also using Meson. For example, I'd like to have:
Related question: is it possible to tell PDM that some optional dependency groups should not be included by default in the lock file?
The text was updated successfully, but these errors were encountered: