diff options
author | Christian Tismer <tismer@stackless.com> | 2018-10-09 10:43:09 +0200 |
---|---|---|
committer | Christian Tismer <tismer@stackless.com> | 2018-10-10 17:36:28 +0000 |
commit | c6395441a1df9b1cc59716b9dad18973bcb72c69 (patch) | |
tree | 335e29dbb0f5f24ad9894d68103ee1ce98af3e77 /keyword-errors.lst | |
parent | 03cef2411c670aa41f448f44edd5abc79107099c (diff) |
Signature: Produce Correctly Nested Python Interfaces
The signature extension has been around for a while.
As more and more demands arise, the quality of the generated
signatures becomes more demanding:
All signatures seem quite correct in PySide. But when testing
the shiboken signatures, some weird results occurred.
It turned out that nested classes were correctly handled by
the code generator, but the produced signatures were quite
wrong. Example:
Before the patch: sample.ValueIdentity.multiplicator()->int
After the patch: sample.Photon.ValueIdentity.multiplicator()->int
This quirk becomes an issue, because now signatures are
replacing the internally generated TypeError messages.
Task-number: PYSIDE-510
Task-number: PYSIDE-795
Change-Id: I16a26ecc2a2d384cb3184144d3934b2606723d53
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Diffstat (limited to 'keyword-errors.lst')
0 files changed, 0 insertions, 0 deletions