Description
In qdom.h:
// Qt extensions QString toString(int = 1) const; QByteArray toByteArray(int = 1) const;
While not ideal that public-facing methods have nameless parameters, it is not a major problem, as the Doxygen documentation is populated in the definition file.
However, PySide, via Shiboken, does attempt to source parameter names automatically from the target header files. Since the names are missing, arg__1 placeholders are automatically provided in the Python bindings for these two methods (see https://doc.qt.io/qtforpython-6/PySide6/QtXml/QDomDocument.html#PySide6.QtXml.PySide6.QtXml.QDomDocument.toString).
Although PySide could work around it [by modifying the function in the value type to provide names manually], it would probably make sense to apply the fix in Qt instead, which could be as trivial as:
// Qt extensions - QString toString(int = 1) const; - QByteArray toByteArray(int = 1) const; + QString toString(int indent = 1) const; + QByteArray toByteArray(int indent = 1) const;
Attachments
Issue Links
- relates to
-
PYSIDE-2967 QCommonStyle: Documentation does not match public interface in C++
-
- Closed
-
-
QTBUG-121670 QDom related classes with anonymous parameters make PySide 6 bindings awkward to use
-
- Closed
-