Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#32707 - [clang] ship python bindings to libclang
Attached to Project:
Arch Linux
Opened by Mr.Magne (Mr.Magne) - Friday, 16 November 2012, 15:16 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 09 January 2014, 13:19 GMT
Opened by Mr.Magne (Mr.Magne) - Friday, 16 November 2012, 15:16 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 09 January 2014, 13:19 GMT
|
DetailsHello,
Is there any reason not to ship python bindings (cindex.py) with clang (or in it's own package) ? If not it would be great to have it :) |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Thursday, 09 January 2014, 13:19 GMT
Reason for closing: Implemented
Additional comments about closing: Included in clang 3.4-1 (currently in [testing]).
Thursday, 09 January 2014, 13:19 GMT
Reason for closing: Implemented
Additional comments about closing: Included in clang 3.4-1 (currently in [testing]).
At this point, manually copying the 'bindings/python/clang' directory to '/usr/lib/python2.7/site-packages' is not something I'd consider doing.
If you want to use libclang in a Python project, you can include the bindings in your source code.
First your suggestion for including the binding in the programs code has the problem that the bindings are incompatible between different versions of libclang meaning the program would have to ship lots of different versions
And secondly this thread http://clang-developers.42468.n3.nabble.com/Calling-clang-packagers-Do-you-install-libclang-amp-the-python-bindings-td4026331.html gives a good suggestion of putting the python libclang bindings in another package