FS#80272 - [clang15] please add python bindings
Attached to Project:
Arch Linux
Opened by M. Greyson Christoforo (greyltc) - Thursday, 16 November 2023, 20:35 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:26 GMT
Opened by M. Greyson Christoforo (greyltc) - Thursday, 16 November 2023, 20:35 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:26 GMT
|
Details
Hi, it would be great if this package shipped with python
bindings just like how the clang package does, only with the
python module renamed to avoid conflicts. clangXX where XX
is 15 in this case. I've made an AUR package to work around
these missing bindings:
https://aur.archlinux.org/packages/python-clang15
Thanks! |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:26 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/clang15/issues/1
Saturday, 25 November 2023, 20:26 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/clang15/issues/1
[1]: https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/pull/1730
[2]: https://github.com/JuliaLang/julia/pull/51720
That sounds like an argument against packaging any of the out-of-date clang/llvm stuff.
I think if we're going to package them, their features should match what the non-out-of-date packages provide. Including the python bindings here rather than in the AUR ensures their versions are synchronized/matching which seems good.
> That sounds like an argument against packaging any of the out-of-date clang/llvm stuff.
clang15 is packaged while other packages are incompatible with the clang 16 release. Similarly gcc12 is packaged but the split package only contains gcc12, gcc12-fortran, gcc12-libs while gcc contains additionally gcc-ada, gcc-d, gcc-go, gcc-objc, lib32-gcc-libs, libgccjit, lto-dump.