libmambapy: Switch build backend to scikit-build-core
#3802
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
setuptools-scm
because it is simpler to configure for now. I don't think the reading version from python file is supported inscikit-build-core
yetsrc/libmambapy/bindings
tobindings
because it interferes withpip install -e
. It is cleaner to have the compilation source outside of the pure python files.Other than that it should be effectively identical.
I did not review the build system, but at least there is an immediate issue that needs to be resolved
This breaks all sdist builds because the archive starts from
libmambapy
folder. In practice, this is a purely developer option and there are neater ways to create one using targets instead. But if you really wish to keep it in that form, a solution is to make a symlink of the cmake folder.Closes #3798