How to Install and Uninstall python310-AnyQt Package on openSuSE Tumbleweed
Last updated: November 07,2024
1. Install "python310-AnyQt" package
This guide let you learn how to install python310-AnyQt on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python310-AnyQt
Copied
2. Uninstall "python310-AnyQt" package
Learn how to uninstall python310-AnyQt on openSuSE Tumbleweed:
$
sudo zypper remove
python310-AnyQt
Copied
3. Information about the python310-AnyQt package on openSuSE Tumbleweed
Information for package python310-AnyQt:
----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python310-AnyQt
Version : 0.2.0-3.2
Arch : noarch
Vendor : openSUSE
Installed Size : 334.3 KiB
Installed : No
Status : not installed
Source package : python-AnyQt-0.2.0-3.2.src
Upstream URL : https://github.com/ales-erjavec/anyqt
Summary : PyQt4/PyQt5 compatibility layer
Description :
PyQt4/PyQt5 compatibility layer.
Features include:
* At the top level, AnyQt exports a Qt5 compatible module namespace along with
some minimal renames to better support portability between different
versions.
* The "QT_API" environment variable controls which Qt API/backend is used.
* The API can be chosen/forced programmatically (as long as no
PyQt4/PyQt5/PySide was already imported).
* An optional compatibility import hook that denies imports from
conflicting Qt APIs, or intercepts and fakes Qt4 API imports to use a Qt5
compatible API (some monkey patching is involved).
----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python310-AnyQt
Version : 0.2.0-3.2
Arch : noarch
Vendor : openSUSE
Installed Size : 334.3 KiB
Installed : No
Status : not installed
Source package : python-AnyQt-0.2.0-3.2.src
Upstream URL : https://github.com/ales-erjavec/anyqt
Summary : PyQt4/PyQt5 compatibility layer
Description :
PyQt4/PyQt5 compatibility layer.
Features include:
* At the top level, AnyQt exports a Qt5 compatible module namespace along with
some minimal renames to better support portability between different
versions.
* The "QT_API" environment variable controls which Qt API/backend is used.
* The API can be chosen/forced programmatically (as long as no
PyQt4/PyQt5/PySide was already imported).
* An optional compatibility import hook that denies imports from
conflicting Qt APIs, or intercepts and fakes Qt4 API imports to use a Qt5
compatible API (some monkey patching is involved).