diff options
| author | Christian Tismer <tismer@stackless.com> | 2022-05-25 15:53:26 +0200 |
|---|---|---|
| committer | Christian Tismer <tismer@stackless.com> | 2022-05-27 13:30:35 +0200 |
| commit | 3bd132cbaf01fe1e929e1279d5b32b3c412cdcf4 (patch) | |
| tree | 2563ce91436a9f90e8ae497f676ec0e9bdf6a458 /build_scripts/main.py | |
| parent | dc55de238c0c7c52812ec4203471e4b2a7f0805d (diff) | |
PyEnum: Fix the old Enums to produce correct .pyi files, again
Before starting the PyEnum move, I always used Python to check
the validity of everything in a .pyi file. I tried that with
Qt enums as well, but it crashed when tested. Therefore,
I did the transition to Python enums, prematurely.
Later on, it became clear that .pyi files are no longer compatible
to be run in Python at all, and Mypy is the checker, instead.
After removing the Python self-test, the original, correct
enum handling can be restored. Depending on PySide version,
the .pyi files are now correctly created for old or new Enums.
[ChangeLog][PySide6] Enums are now correctly handled in Python
interface files, depending from the version selection.
Change-Id: I79acc4d12b3c16e2624fbb0a6147bbeb40075ebb
Fixes: PYSIDE-1731
Pick-to: 6.3
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Diffstat (limited to 'build_scripts/main.py')
0 files changed, 0 insertions, 0 deletions