[clang] [llvm] [libclang/python] Enable packaging libclang bindings (PR #125806)
Cristian Le via cfe-commits
cfe-commits at lists.llvm.org
Wed Mar 5 11:14:04 PST 2025
LecrisUT wrote:
> - The python bindings aren't placed in the right folder to import them when the package is pip installed
They are *not*? I tried it and it imported fine, same as you noticed.
> - Installing directly from a git URL or source archives for a release won't work
Similarly, aren't the subpoints proving that it does work?
> - The version number detected when building a wheel for tagged releases isn't correct
Yes there are multiple version schemas that are controlled by `tool.setuprools_scm.version_scheme = "no-guess-dev"`. See [here](https://setuptools-scm.readthedocs.io/en/latest/extending/#available-implementations) for what's available. The `.post1` or such are intentional in order to evaluate higher than the last release. Personally I go with `guess-next-dev`, since it does a sensible job.
Also, I thought you've already added the fallback-version. We should be fine to add it back just in case.
https://github.com/llvm/llvm-project/pull/125806
More information about the cfe-commits
mailing list