dgit.raspbian.org Git - pyside2.git/log

Merge pyside2 (5.15.2-2.3) import into refs/heads/workingbranch

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.

Gbp-Pq: Name test-with-current-interpreter.patch

shiboken6: Adapt to LLVM 12.01

The identifier for anonymous enums has been changed, causing
shiboken to no longer recognize them.

(cherry picked from commit 1948a1b6f9a3547ba9fba9b8c525eb6e1c6b4f13)

Gbp-Pq: Name shiboken6-Adapt-to-LLVM-12.01.patch

py3.10-prep: Fix a very old refcounting error in time_test.py

Since 2012-03-08, there was a refcounting error in
the typesystem_sample.xml file at <value-type name="Time">.
The boolean function results were not refcounted.

(Commit 7b731d702c64d172e192aa1876e4a6fade6c38d7)

This bug was hard to find because nobody expects a failure in the
testing code, and the error shows up at the very end in the
finalization code, totally unrelated to the error location.

In order to find it, the setting `PYTHONMALLOC=malloc` was needed,
because otherwise we got a Python memory dump but no traceback.
Then, Python was modified and code was inserted in the various
involved `code_dealloc`, `tupledealloc` and `object_dealloc`
functions that printed the involved refcounts and types before
performing the actual deallocation.

This bug actually was of no harm since only the wrong test was
involved. It was very misleading because there were quite some
changes to the `datetime` module in Python 3.10. But the bug
was nothing but a dormant refcounting error.

(cherry picked from commit 2af6ac20de365116b52b65c6c34cfd6c536c23df)

Gbp-Pq: Name py3.10-prep-Fix-a-very-old-refcounting-error-in-time_test.patch

py3.10-prep: Finally support Python 3.10

After the major problems are solved in
    py3.10-prep: re-implement zip import
    py3.10-prep: reset the type cache after feature switching
    py3.10-prep: Fix parser.py for changed typing module

, there are only some minor changes left to do. One thing
is still not clear:

* Unsolved: In time_test.py, the last two tests work but
crash at shutdown.
It is not yet clear if this is a PySide or Python error.

This will crash Python 3.10 if not solved until the release.

(cherry picked from commit 81e9cff884d6b03cdf64a5dd6ec6564d99177e0c)

Gbp-Pq: Name py3.10-prep-Finally-support-Python-3.10.patch

py3.10-prep: Fix parser.py for changed typing module

The typing module has subtle changes that are not even
documented: Typing types now have a __name__ attribute.
That confused the parser of the pyi generator because
suddenly stingizing

Callable[..., Optional[str]]

resulted in

Callable[..., Optional]

because of special rules that return the generic name
of a typing type, which was very unexpected. Finding this bug
took a lot of debugging of the recursive `_resolve_type`
function.

(cherry picked from commit 2530cb3f165ac02b8f7132e3f5ab4f7f6896dbd9)

Gbp-Pq: Name py3.10-prep-Fix-parser.py-for-changed-typing-module.patch

py3.10-prep: reset the type cache after feature switching

When using feature switching in Python 3.10, there were
funny effects where switched and un-switched versions appeared
to co-exist.

It turned out that we were hit by function caching that
is now implemented for the LOAD_ATTR opcode.

It was not known that caching would happen at all for
PySide classes because we don't use Py_TPFLAGS_VALID_VERSION_TAG.
But actually, this flag is used internally by Python to do some
optimizations, and we just have to notify the interpreter of
type changes by PyType_Modified().

(cherry picked from commit 3a2b7c6f88bba04d8b7ddb571163d23c15c36a4f)

Gbp-Pq: Name py3.10-prep-reset-the-type-cache-after-feature-switching.patch

qApp: fix flag handling in Python 3.8+ and a Python 3.9 issue

This is an old problem that was solved for Python 2.7.
From Python 3.8 on, the behavior is the same with Python 3.

The fix finally was to extend a Python 2.7 patch to Python 3
as well. See the Jira issue for details.

This patch includes also a small patch that was mentioned as
necessary for Python 3.9: Python issue 40217. I have seen no
effect of this change yet but applied the patch, anyway.

Origin: https://codereview.qt-project.org/c/pyside/pyside-setup/+/328046

Gbp-Pq: Name qApp-fix-flag-handling.patch

Pass --reuse-build only to commands that use DistUtilsCommandMixin

This is a concatenation of two upstream commits:
- https://code.qt.io/cgit/pyside/pyside-setup.git/commit/?id=ed0571df854a232e
- https://code.qt.io/cgit/pyside/pyside-setup.git/commit/?id=3f00c2adad2e38b0

Gbp-Pq: Name fix-reuse-build.patch

Blacklist failing tests

Forwarded:
https://bugreports.qt.io/projects/PYSIDE/issues/PYSIDE-1146?filter=allopenissues

Gbp-Pq: Name blacklist-failing-tests.patch

Fix spelling errors

Last-Update: 2018-07-12

Gbp-Pq: Name fix-spelling-errors.patch

Update import of PyQt5 private sip module and remove Python 2/PyQt4 setapi calls

Last-Updated: 2020-12-20

Gbp-Pq: Name update-sip-import.patch

pyside2 (5.15.2-2.3) unstable; urgency=medium

* Call "py3versions -d" instead of "py3versions -r" in tests.
*

[dgit import unpatched pyside2 5.15.2-2.3]

Import pyside2_5.15.2-2.3.debian.tar.xz

[dgit import tarball pyside2 5.15.2-2.3 pyside2_5.15.2-2.3.debian.tar.xz]

Merge pyside2 (5.15.2-2) import into refs/heads/workingbranch