| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| update-sip-import.patch | Update import of PyQt5 private sip module and remove Python 2/PyQt4 setapi calls | Kurt Kremitzki <kkremitzki@debian.org> | no | |||
| fix-spelling-errors.patch | Fix spelling errors | Sophie Brun <sophie@freexian.com> | no | 2018-07-12 | ||
| blacklist-failing-tests.patch | Blacklist failing tests Forwarded: https://bugreports.qt.io/projects/PYSIDE/issues/PYSIDE-1146?filter=allopenissues |
Sophie Brun <sophie@freexian.com> | no | 2019-11-22 | ||
| test-with-current-interpreter.patch | Find the build directory matching the current interpreter This is needed to allow us to run tests with all supported Python versions. Without this patch, the latest build directory will be always picked, no matter what the current interpreter is. |
Dmitry Shachnev <mitya57@debian.org> | no | 2021-11-14 | ||
| Shiboken-Fix-the-oldest-shiboken-bug-ever.patch | Shiboken: Fix the oldest shiboken bug ever which shows up on Python 3.11 b7df2f1c0 "Fix signal initializer.", 18. May 2010 at 00:55 There was a `PySequence_Check` in the evaluation of some signature function parameter processing, which should have been `PyTuple_Check`. Since the new PyEnums are also sequences, the new optimization in Python 3.11 changed the parameter handling in a correct way and replaced the argument tuple by a direct single argument of an enum type. And that is also a sequence ... There are probably still dormant issues like this in the codebase which gives reason to submit a task that checks all Python interface functions for correctness. (cherry picked from commit 2720e01f21f3771cb755ef183b8160f691bdb575) |
Christian Tismer <tismer@stackless.com> | no | 2022-06-21 | ||
| PyEnum-make-forgiving-duplicates-work-with-Python-3.11.patch | PyEnum: make forgiving duplicates work with Python 3.11 There was a silent change in PyEnums that turns Enum attributes into properties. This does not harm the Python interface but needed some change in the duplication emulation. Furthermore, new internal enums are created with an underscore name. The meta class was changed from EnumMeta to EnumType. [ChangeLog][shiboken6] The new Python Enums are now compatible with Python 3.11 (cherry picked from commit da2cf031521815a9559ca784beadb70c7a2852d9) |
Christian Tismer <tismer@stackless.com> | no | 2022-06-21 | ||
| Python-3.12-Fix-the-structure-of-class-property.patch | Python 3.12: Fix the structure of class property There is a PySide bug in Python 3.10 already: The structure for classproperty derives from the property structure. This was extended in Python 3.10, already, but the type generation check was made more exhaustive in Python 3.12 and recognized that. This change is only for making the compiler/C API happy. In order to use the extension field, it is necessary to do a runtime check because of the Limited API. (cherry picked from commit edfd9a5ad174a48f8d7da511dc6a1c69e931a418) |
Christian Tismer <tismer@stackless.com> | no | 2023-02-14 | ||
| Support-running-PySide-on-Python-3.12.patch | Support running PySide on Python 3.12 Builtin types no longer have tp_dict set. We need to use PyType_GetDict, instead. This works without Limited API at the moment. With some great cheating, this works with Limited API, too. We emulate PyType_GetDict by tp_dict if that is not 0. Otherwise we create an empty dict. Some small changes to Exception handling and longer warm-up in leaking tests were found, too. (cherry picked from commit 441ffbd4fc622e67acd81e9c1c6d3a0b0fbcacf0) |
Christian Tismer <tismer@stackless.com> | no | 2023-02-14 | ||
| Final-details-to-enable-3.12-wheel-compatibility.patch | Final details to enable 3.12 wheel compatibility (cherry picked from commit 6c7bb7b6e1008909e49bc04d2a48024309a784cc) |
=?utf-8?q?Cristi=C3=A1n_Maureira-Fredes?= | no | 2023-10-10 | ||
| Stop-using-imp-module.patch | Stop using imp module Part of commit e796600c9663a26ccf1929aca8336eb0cb23fe5d. |
Friedemann Kleint <Friedemann.Kleint@qt.io> | no | 2020-09-03 | ||
| Do-not-change-RPATH.patch | Do not change RPATH | Dmitry Shachnev <mitya57@debian.org> | not-needed | 2024-01-25 | ||
| shiboken2-clang-Fix-clashes-between-type-name-and-enumera.patch | shiboken2/clang: Fix clashes between type name and enumeration values Remove all constant and enum value type entries found in the type lookup unless it is looking for template arguments; where it may be a non-type template argument. (cherry picked from commit e22f717153a5e9855531f45c0bf82ff2461a3f7e) |
Friedemann Kleint <Friedemann.Kleint@qt.io> | no | 2023-04-25 | ||
| shiboken2-clang-Fix-and-simplify-resolveType-helper.patch | shiboken2/clang: Fix and simplify resolveType() helper The function had a bug which only manifested with clang 16: "type" should have been assigned the type of the cursor obtained from clang_getTypeDeclaration(). With this, the complicated lookup code in getBaseClass() can be removed. |
Friedemann Kleint <Friedemann.Kleint@qt.io> | no | 2023-04-25 | ||
| shiboken2-clang-Remove-typedef-expansion.patch | shiboken2/clang: Remove typedef expansion The functionality will be re-added by a subsequent change expanding elaborated types. (cherry picked from commit 24742dca014109bd3c2a9775fc15ca306ab22c9c) |
Friedemann Kleint <Friedemann.Kleint@qt.io> | no | 2023-04-20 | ||
| shiboken2-clang-Fix-build-with-clang-16.patch | shiboken2/clang: Fix build with clang 16 clang 16 returns more elaborated types instead of fully qualified type names. Qualify elaborated types when retrieving the type name. [ChangeLog][shiboken6] Support for libclang version 16 has been added. (cherry picked from commit 44ef1859214c66861a251d4a0faf5c38dc050850) |
Friedemann Kleint <Friedemann.Kleint@qt.io> | no | 2023-04-25 | ||
| shiboken2-clang-Record-scope-resolution-of-arguments-func.patch | shiboken2/clang: Record scope resolution of arguments/function return Add a flag indicating whether a type was specified with a leading "::" (scope resolution). Such parameters previously caused the function to rejected due to the "::TypeName" not being found. The type resolution added for clang 16 strips these qualifiers though, so, the information needs to be stored. (cherry picked from commit 075d8ad4660f05e6d2583ff1c05e9987ad624bfe) |
Friedemann Kleint <Friedemann.Kleint@qt.io> | no | 2023-04-27 | ||
| shiboken2-clang-Suppress-class-scope-look-up-for-paramete.patch | shiboken2/clang: Suppress class scope look up for parameters with scope resolution Add a flag to AbstractMetaBuilderPrivate::findTypeEntriesHelper() to suppress the class scope look in case scope resolution. |
Friedemann Kleint <Friedemann.Kleint@qt.io> | no | 2023-04-27 | ||
| shiboken2-clang-Write-scope-resolution-for-all-parameters.patch | shiboken2/clang: Write scope resolution for all parameters of native wrappers Make sure types are correct for cases like: - QtDBusHelper::QDBusReply::QDBusReply(::QDBusReply<void>) - Qt3DInput*Event constructors taking the equivalent QtGui classes (Qt3DInput::QMouseEvent(::QMouseEvent *); [ChangeLog][shiboken6] Support for parameters/function return types with scope resolution has been improved. (cherry picked from commit dd863857436bbeeba4c0a1077f5ad16653296277) |
Friedemann Kleint <Friedemann.Kleint@qt.io> | no | 2023-04-27 | ||
| Modify-sendCommand-signatures.patch | Modify sendCommand signatures to use 0 as default value The original default value was QNodeCommand::CommandId(), and shiboken copies it verbatim from the header file, however it does not work because we do not generate "using namespace Qt3DCore;". 0 is the same as QNodeCommand::CommandId(). |
Dmitry Shachnev <mitya57@debian.org> | no | 2024-02-04 |