Qt for Python (PySide/Shiboken)

no offense but I give up. I read https://doc.qt.io/qtforpython/gettingstarted.html#building-the-documentation , I bothered you many times and I still can't build this fucking doc (some new error that I won't share). So if push some new other changes, I'll push having no idea of what it could looks like. I have no idea how to solve the doc toolchain but as you write it I see how complex it is. Let me take a step back about all this thing: - Pyside is mainly used( I think) by people from the python community. - We (python community) usually contribute to project by forking a repo, make change, push et open a PR. Thats all. Sometimes we don't clone the repo locally simply editing doc online - One day you say "pyside is cool", I'm happy to do a small contribution, but you don't now what's in front of you: create account, accept conditions, sshkeys, discover gerrit, discover gira, read 3 or 4 pages of manuel, to configure locally, trying to push, install the precommit thing, re trying to push. But you pushed some ugly thing because you didn't test it. Then you say : "If I change the doc I'm gonna build it before next push". So you read 3 or 4 others doc pages, make some google search, ask nice people for help. But no it won't work. You spent hours just to add 2 lines in the docs. You feel bad. - me eye on it : maybe all those things are usual and basics in C++ world but really it's very disturbing for "usual" python user. - pyside is supported by a Company and would need to build a big community but with all those pains it'll be hard. - I would add that python users without real C++ background can quite only contribute in docs. So I'm pretty sure that if building docs means always "all those not so easy building steps" they won't help. - Is it not possible to split the "standard doc" outside the "apidoc modules" and run pyton setup.p make_doc or something like that ?