pdm install --no-default
now runs a PEP 517 build (we need to add --no-self
for PDM<=2.8.2 behavior)
#2230
Closed
1 task done
Labels
🐛 bug
Something isn't working
As of PDM v2.9.0,
pdm install --no-default
now runs a PEP 517 build, and we need to add--no-self
to get the old behavior.In PDM v2.8.2,
pdm install --no-default
did not run a PEP 517 build.This seems pretty minor (and I've got no idea if this is a bug, or the old behavior was a bug and the current behavior is the correct one), but I thought it was making an issue anyway, since I can't seem to find it in the v2.9.0 PDM Release notes, and this did break some of our Linting/Documentation Continuous Integration pipelines.
Steps to reproduce
Clone the following GitHub gist, which has a minimal pdm package that always fails to build: https://gist.github.com/aloisklink/54e8047482db16bef4b2177068aede3c
Afterwards, run:
pdm install --no-default
.Actual behavior
In pdm v2.9.0, this installs the dev dependencies, AND causes a PEP 517 build to occur.
Using the above test case, where the build script always fails, you'd get the following output:
verbose logs
Expected behavior
The same behavior as in PDM v2.8.2. E.g.,
pdm install --no-default
installs development dependencies, but DOES NOT RUN A PEP 517 build.It's not too big of a deal, we can easily just add a
--no-self
option, but it's probably worth documenting this change in thev2.9.0
changelog.E.g., in v2.9.0
pdm install --no-default --no-self
works exactly howpdm install --no-default
worked in v2.8.2.verbose logs
Environment Information
The text was updated successfully, but these errors were encountered: