Migrate from pdm-pep517
It is quite easy to migrate from the [pdm-pep517] backend, there are only a few difference between the configurations of the two backends.
pdm-pep517
has renamed the tool.pdm
table to tool.pdm.build
since 1.0.0. If you are still storing the build configurations directly under tool.pdm
table, move them under tool.pdm.build
now. The old table is no longer supported.
setup-script
In pdm-pep517
you are allowed to call a custom build
function during the build to add user-generated contents, which is specified by tool.pdm.build.setup-script
option. However, this option has been dropped in pdm-backend
, use a custom hook instead, and the custom script can be loaded automatically with the name pdm_build.py
.
And if run-setuptools
is true
, pdm-pep517
will instead generate a setup.py
file and call the specified script to update the arguments passed to setup()
function. In pdm-backend
, this can be also done via custom hook:
That's all, no more changes are required to be made and your project keeps working as before.