Picking up pypi name?

[emmatyping]

Hello,

I am quite curious with using clang bindings on a project of mine. I want to be able to support Windows along with MacOS and Linux. Unfortunately, Windows has no official method of distributing clang bindings. Because of this, my best recourse is to put up a package of the bindings on pypi. It seems based on the README your needs are satisfied by your Linux package manager, and you have marked this package as "obsolete". In addition, there hasn't been an update for Clang 6.0. In the interest of maintaining an easily installable, up to date set of Python bindings to clang, would you be willing to pass on ownership of the clang PyPI name to me to maintain? If you are interested please let me know here or via email ethan [at] ethanhs [dot] me. Finally I wanted to thank you for the work you have done on maintaining this package.

Sincerely,
Ethan Smith

[sighingnow]

Hi @trolldbois @ethanhs,

Many thanks for your work for updating the pypi clang package to 6.0.0 and make it available for people. However the clang package on pypi hasn't been updated since 2018, now the LLVM has released version 10.0.

I want to use clang python binding as a dependency of my project and I want the libclang could be accessed easier for Python users. I'm considering upload the libclang python bindings along with prebuilt libclang.so (or libclang.dylib) for different platforms to make the install process easier.

Could I pike up the pypi package name ? Or could you please add me to the maintainer list of the pypi package as well? My email address is sighingnow@gmail.com, the user name is sighingnow.

Thanks in advance!

[emmatyping]

Yeah, sorry I've had so little time to work on it. Please let me know if you end up releasing packages!

[trolldbois]

@ethanhs @sighingnow I just published a bunch of version, pulling directly from the debian packages. tell me if it works for you. I'll update the github repo here with the simple download & packaging script

[sighingnow]

Hi @trolldbois, I have publish my package under the name libclang: https://pypi.org/project/libclang/#files, a prebuilt staticly linked libclang.{dll,so,dylib} (which only requires libc, without any extra dependency) is bundled in wheel packages for different platforms (Win,Linux,Mac).

Which means, a Python user doesn't need to install clang-llvm package (using system-wide package manager or whatever) to make full use of clang.cindex package interface (Somtimes installing a latest clang-llvm release (and find the correct location of libclang.{dll,so,dylib}) is not easy). Could I pick up the pypi name and replacing the clang package on pypi with the content of the package libclang?

Thanks!

[sighingnow]

Hi @trolldbois,

After several release round it looks like the libclang (https://pypi.org/project/libclang/#files) works well for our python users, because it has no other system-wide package dependency (libclang-dev or libclang-devel, and such things). Just pip install will gather all things correctly.

However because the naming clang vs. libclang, we often mis-install the clang pip package instead. Thus I'm wondering if there are any possible for such a collobration to publish the content of current libclang under the name of clang to pypi?

[sighingnow]

And there won't be any conflict. We just need to add some wheel artifacts.

[trolldbois]

@sighingnow I think the clang python package should not distribute Binary Libraries by default.
But I can understand the need for your package/distribution also.
Maybe we could make it an extra ?
pip install clang[libclang] -> install_requires libclang