-
-
Notifications
You must be signed in to change notification settings - Fork 421
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
setuptools backend does not find PROJECT_ROOT dependencies #1927
Comments
The relative path is backend-specific, setuptools doesn't support it, so we can't do anything here. |
Alright, thanks for the clarification. I think my workaround will be to split it into a C extension project that doesn't depend on the rest and a pure python one that does. Do you think temporarily changing to setuptools backend only during |
@timdiels-ontoforce why not pdm-backend? it also supports calling setuptools for building C extension: https://pdm-backend.fming.dev/hooks/#call-setup-function-to-build-extensions |
Ah great I'll try that, I somehow overlooked that in the docs when searching for "C extension". I then stumbled upon an old discussion on this repo suggesting to use setuptools backend. |
Thanks, that works. I see why I overlooked it, did not realize there's a separate docs site for pdm-backend, only searched the pdm one. |
Basically the same as #1658 but it's closed and we do need setuptools to build a C extension so we can't use the workaround.
Steps to reproduce
pdm lock -vv
Actual behavior
Expected behavior
It works with pdm-backend, but with the setuptools backend it apparently does not substitute
${PROJECT_ROOT}
. Once that's fixed, you might want to check that it can also handle a relative path. An absolute path, withoutPROJECT_ROOT
, worked for me.Environment Information
The text was updated successfully, but these errors were encountered: