Python bindings for Qt
http://wiki.qt.io/Qt_for_Python
The PySide2 project provides Python bindings for the Qt
application and UI framework.
-
1
derived packages
- Links to KDE:Qt5 / python3-pyside2
- Has a link diff
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout KDE:Qt:5.15/python3-pyside2 && cd $_ - Create Badge
Refresh
Refresh
Source Files (show unmerged sources)
| Filename | Size | Changed |
|---|---|---|
| 0001-Always-link-to-python-libraries.patch | 0000001545 1.51 KB | |
|
0001-Don-t-try-to-install-or-use-uic-rcc-designer- |
0000001866 1.82 KB | |
|
0001-Fix-tests-sample_privatector-sample_privatedt |
0000001416 1.38 KB | |
|
0001-cmake-Don-t-assume-qhelpgenerator-is-in-PATH. |
0000002564 2.5 KB | |
| _constraints | 0000000166 166 Bytes | |
| _multibuild | 0000000067 67 Bytes | |
| pyside-setup-opensource-src-5.15.12.tar.xz | 0003585204 3.42 MB | |
| python3-pyside2.changes | 0000026942 26.3 KB | |
| python3-pyside2.spec | 0000011269 11 KB |
Latest Revision
buildservice-autocommit
accepted
request 888020
from
Christophe Giboudeaux (cgiboudeaux)
(revision 4)
Christophe Giboudeaux (cgiboudeaux)
(revision 4)
auto commit by copy to link target
Comments 2
@bnavigator If I want to force using python 3.11 on TW, is changing
%define pythons python3enough?upstream won't support 3.12 (https://wiki.qt.io/Qt_for_Python#Python_compatibility_matrix)
~Better use
%define skip_python312 1and~ make sure all consumers never want a python3-pyside2 when the primary python changes to python312.~Going back from a python311-pyside2 package to python3-pyside2 will need an extra obsoletes line.~
Edit: I just realize that pyside*2* never was enabled for multibuild like pyside6. Disregard my comment above.
%define pythons python311andObsoletes: python3-pyside2 < %{version}-%{release}is the right move here. Same for the consumers