You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
[project.optional-dependencies]
# so that users can run `pip install fluidfft[fftw]`
# However, it should not be included in the lock file because for development
# we want to install fluidfft-fftw from source
fftw = ["fluidfft-fftw"]
[tool.pdm.dev-dependencies]
# we want to have this one in the lock file
# fluidfft-fftw uses Meson and should be installed in editable mode with `--no-build-isolation`
plugins = [
"-e fluidfft-fftw @ file:///${PROJECT_ROOT}/plugins/fluidfft-fftw",
]
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:
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: