Richard Shaw wrote:
> Any progress on this? I can submit a BZ ticket for tracking if needed.
A pull request would be easier, then I would just have to hit a button. :-)
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsu
On Thu, Jul 13, 2023 at 5:10 PM Kevin Kofler via devel <
devel@lists.fedoraproject.org> wrote:
> Richard Shaw wrote:
> > # FIXME This patch is completely meaningless in the context of C++.
> > # It is a workaround for a pyside2 build failure with Qt 5.15.9,
> > # pyside2 5.15.9, clang 16.0.1 -- th
Richard Shaw wrote:
> # FIXME This patch is completely meaningless in the context of C++.
> # It is a workaround for a pyside2 build failure with Qt 5.15.9,
> # pyside2 5.15.9, clang 16.0.1 -- the generated code thinks a
> # not otherwise specified "Type" is in fact a
> # QFlags, causing many funct
I was able to work around that error but now hitting the following, and the
crumb trail I followed seems to indicate that this needs to be fixed in
Qt5, not PySide2[1]
In file included from
/builddir/build/BUILD/pyside-setup-opensource-src-5.15.10/redhat-linux-build/sources/pyside2/PySide2/QtGui/P
Richard Shaw wrote:
> So it looks like upstream has no intention of supporting Python 3.12 in
> Pyside2 (5.15.x series), only in Pyside6 which AFAIK requires Qt6.
>
> https://bugreports.qt.io/browse/PYSIDE-2388
>
> Porting is non-trivial and Python upstream does not provide a porting
> guide.
>
So it looks like upstream has no intention of supporting Python 3.12 in
Pyside2 (5.15.x series), only in Pyside6 which AFAIK requires Qt6.
https://bugreports.qt.io/browse/PYSIDE-2388
Porting is non-trivial and Python upstream does not provide a porting guide.
https://docs.python.org/3/c-api/unic