Qt for Python (PySide/Shiboken)

maybe one of the points is that usually in python projects the process are fast and straightforward, like I clone something/fork do some changes, run the tests, and they run in a couple of minutes, and I can I don't know generate some other things, etc, and you can submit some patch verifying everything. The problem in this case, and in any project that provide bindings to C or C++ libraries, is that you need to deal with the whole overhead from it. Personally, as a PySide dev, I need to have several Qt versions compiled, and installed from the installer on my system, I need to have many Python environments, and different versions, and try little features in many different situations. It was hard, and time wasting at the beginning, because I was not used to it, but now it's simpler. The problem here is that I have no idea on how to make the building process simpler than now, and that's why the curve is so steep for people which is not used to C++ development environments to collaborate. I really would love to have something like "python gen_bindings.py" or "python build_docs" but still, I don't see how to speed up the process of querying the Qt installation, get information from the headers, modify and generate C++ wrappers, and compile that for Python to use it. Maybe the option I pointed out, to only build 'Core' helps, but still you need to take care of having 'libclang', properly setup. For the docs, it's again the same story, we need to parse the whole Qt framework to get the API documentation, and on top modify some snippets to provide python code. On that front, maybe one can provide a way to build the docs without Qt API and in that case it will be only a python-sphinx run, but we don't have the resources to do it. Yes, The Qt Company is a company, but at the moment the devs have 2 keyboards, one for the hands and other for the feet, because there are a lot of things to do and check towards Qt6. Yes, this is not the users problem, but it's just an explanation why I cannot sit and try to see how to improve the collaborators experiences without finishing other high priority tasks. But to be honest, I would love to be payed for that, I really believe it's crucial for the project to evolve, but we don't have the resources, since as you might now, you don't get charged to use PySide2 normally, only paying costumers, and they are a little little fraction in Qt. So a project that is 99% open source as pyside (because we provide like 3 commercial modules) cannot justify having a team of 5 people working on this. All the documentations tweaks, or interaction you see here, from my side, or IRC is purely me, since I could easily do my 9am-5pm job and forget about. At the moment the only "contribution" to the community I'm able to do, is to answer questions here time to time, and spend some hours on the weekend for adding stuff to the tutorials or examples, or preparing talks for local meetups :/