I know there are a few different Python projects/bindings published to PyPI, as well as a PyPI LLVM org ( Profile of LLVM · PyPI ). However, it looks like none of the projects live under the LLVM org on PyPI. Who would be the person to contact about getting a PyPI project moved from an individual user account into the LLVM org?
One of the challenges with several packages I’ve been looking at updating on PyPI is that the maintainers are mostly MIA. While I could potentially try to take over maintenance of them myself, it would be better if they can live under a more “official” LLVM org that has several people in it who can handle issues that arise if the maintainer of an individual project disappears.
This is something I’ve wanted to do for a while. If you have a project published solely from monorepo sources, please reach out so we can transfer it over.
Great, I’ll try to let the current maintainer(s) for libclang and clang know. Do you want me to cc you on an email to them or tag you on a relevant GitHub issue (that I hope they will eventually see)?
For reference, below this is the current status on trying to reach the sole maintainers for both of those projects.
trolldbois has said he’s willing to transfer pypi clang release/trusted publishing over when things get some traction on the LLVM side, so that’s hopefully just a matter of getting him the info needed to do the transfer (and perhaps see about transferring the repo GitHub - trolldbois/python-clang: Python bindings for clang from clang HEAD or creating a fork under the LLVM org?)
For libclang, sighingnow is fairly unreachable; after ~6 months waiting to hear from him, in June he said he’d add me as a maintainer then disappeared again. I’ll give him an update on this, but not counting on hearing anything. I have a PEP 541 request ( PEP 541 Request: libclang · Issue #8202 · pypi/support · GitHub ) open for transferring maintainership of the PyPI package – I can update the request to point to one of your accounts and a repository under the LLVM GitHub org.
For trolldbois/python-clang I already converted the pyproject.toml file over to work with the existing source code and git tags in the LLVM monorepo, and plan on adding the relevant CI workflows in a subsequent PR – however it seems to be stuck with not having the right set of reviewers.
I could do a more direct migration of the code into the monorepo with minor adjustments if you think that would be easier for getting reviewers. Some things are much cleaner with the pyproject.toml and workflows being rewritten to take advantage of the monorepo structure.
The libclang packaging code might be even more of a hack initially.