Details
-
User Story
-
Resolution: Unresolved
-
P1: Critical
-
None
-
None
-
None
-
4315cfb44 (dev), 04ebdcb6e (6.4), 4caf38c27 (tqtc/lts-6.2), 0479b02b6 (dev), 4fbcfa43a (6.4), 088acf9ae (dev), 985c281c2 (6.4), 99f1b42b3 (dev), e48afcb0d (6.4), 3c60c8efa (tqtc/lts-6.2), 2160cefd6 (dev), c2c11d067 (dev), 7565650d8 (dev), 225aa4238 (dev)
Description
Building the documentation requires the following steps: https://wiki.qt.io/Qt_for_Python/GettingStarted#Building_the_Documentation
The toolchain works as follows:
- qdoc is run with .webxml output format
- shiboken runs over the webxml pages and extracts the parts for which bindings exist (according to its type system) and potentially applies modifications and outputs .rst
- Referenced C++ code snippets are translated to Python using a regexp-based tool
- sphinx is run to generate the HTML docs from the .rst files produced and other, fixed pages provided (tutorials etc)
Attachments
Issue Links
- relates to
-
PYSIDE-1112 Improve Qt for Python documentation
- Open
-
QTBUG-86987 qdoc doesn't recognize hidden friends as available APIs
- Closed
-
PYSIDE-2111 A lot of pages look like an automatic translation of the C++ documentation
- Closed
- mentioned in
-
Page Loading...