Call for maintainers

[sizmailov]

I've started pybind11-stubgen when there were no good alternatives to make good enough stubs for pybind modules.
As of today I don't have a C++ project that needs python bindings, so I'm a bit out of touch with recent pybind/python changes that affect the project and don't have enough hours.

At this point I think it's meaningful to ask if anyone might volunteer to maintain the project.

To make as transparent as possible I'd like to share my view on the project.

The original goal of the project was to make it C++ extensions seamless to use in python.
This includes a few things:

• Syntactically correct stubs (even for the code with binding errors).
• Hints for fixing the binding code when possible (writing binding code is not an easy task)
• Compatibility with static checkers (mypy / pyright) and IntelliSense

It's a challenging task for a number of reasons. C++ and Python do not perfectly match and there are a number of issues in python typing system that prevents one from expressing. That lead to a few hard-coded decisions.

I'd like to keep the CLI interface minimal and support only a handful options to be reasonably good for a generic project and provide pybind11-stubgen as a library to enable any custom fine-tuning. It would be great if we could keep it that way.

I hope a couple of people might be interested and we'll figure out how to move forward with it.

[parker-research]

I could potentially help out a bit with this. Also don't have a ton of time, but am using it with the slang project at the moment, and am becoming pretty familiar with it.

[ax3l]

@sizmailov thank you for all the work on this project!

I do not have a ton of time and I have not fully understood the structure of this project yet. If you have a chance to write some developer docs that would help me to get more into it, as I rely more and more on it in my work. Things like: how does this project parse and operate pybind11 modules and how is it structured. Maybe also a few inline API docs for central functions.

That said, I could already help with tasks like CI.

[virtuald]

I depend on this project for robotpy/semiwrap so once I run into something I can't get around I'll just fork it as robotpy-pybind11-stubgen ;)

It probably makes sense to transfer it over to the pybind11 org and that team can choose maintainers? I don't have time to add new features (not that it really needs them) but happy to do basic maintainership stuff.

[gentlegiantJGC]

I have created a branch of this project here.
I have updated the build tools and tests including tests for pybind11 v3 for which I have created a pull request in #271.
Ideally the changes made there will get merged back into this repository periodically.
I can review and merge pull requests there but I won't be implementing features myself unless they are needed for my project.