How to Install and Uninstall python38-AnyQt Package on openSuSE Tumbleweed
Last updated: November 26,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "python38-AnyQt" package
Please follow the steps below to install python38-AnyQt on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python38-AnyQt
Copied
2. Uninstall "python38-AnyQt" package
This tutorial shows how to uninstall python38-AnyQt on openSuSE Tumbleweed:
$
sudo zypper remove
python38-AnyQt
Copied
3. Information about the python38-AnyQt package on openSuSE Tumbleweed
Information for package python38-AnyQt:
---------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python38-AnyQt
Version : 0.0.13-1.3
Arch : noarch
Vendor : openSUSE
Installed Size : 263,3 KiB
Installed : No
Status : not installed
Source package : python-AnyQt-0.0.13-1.3.src
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 : python38-AnyQt
Version : 0.0.13-1.3
Arch : noarch
Vendor : openSUSE
Installed Size : 263,3 KiB
Installed : No
Status : not installed
Source package : python-AnyQt-0.0.13-1.3.src
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).