diff options
| author | Christian Tismer <tismer@stackless.com> | 2019-11-13 19:12:16 +0100 |
|---|---|---|
| committer | Christian Tismer <tismer@stackless.com> | 2019-12-20 15:51:55 +0100 |
| commit | 0b6dd91fbd02e4de1f653e2a8cd6e892628dac0c (patch) | |
| tree | 05895f49ccc906fd291d8c1cf2d3ade96349f188 /examples/xmlpatterns/schema/ui_schema.py | |
| parent | abeb6ecd702244a00be5666c55682211060ec6ea (diff) | |
qApp: Ensure QtCore import when embedded QApplication subclass is used
The qApp machinery works great with Python.
When using embedding, things are different because there
is no longer a wrapper layer.
Unfortunately, many extension modules use C++ to derive a
QApplication class.
This has the side effect that when a foreign C++ module gets
imported, the qApp machinery does not see it as it would
in Python.
Instead of a complex analysis, we always make sure that QtCore
is imported. It will report the right instance, anyway.
This change could not easily be tested.
It was confirmed as a solution by Antonio Rojas.
Change-Id: Ie9c56ac75e6c0ae3ace615dfc26c6d218ff4efea
Fixes: PYSIDE-1135
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Diffstat (limited to 'examples/xmlpatterns/schema/ui_schema.py')
0 files changed, 0 insertions, 0 deletions