How to Install and Uninstall python312-fields Package on openSuSE Tumbleweed
Last updated: December 26,2024
1. Install "python312-fields" package
Please follow the instructions below to install python312-fields on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python312-fields
Copied
2. Uninstall "python312-fields" package
This is a short guide on how to uninstall python312-fields on openSuSE Tumbleweed:
$
sudo zypper remove
python312-fields
Copied
3. Information about the python312-fields package on openSuSE Tumbleweed
Information for package python312-fields:
-----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-fields
Version : 5.0.0-4.6
Arch : noarch
Vendor : openSUSE
Installed Size : 111.9 KiB
Installed : No
Status : not installed
Source package : python-fields-5.0.0-4.6.src
Upstream URL : https://github.com/ionelmc/python-fields
Summary : Container class boilerplate killer
Description :
Container class boilerplate killer.
Features:
* Human-readable ``__repr__``
* Complete set of comparison methods
* Keyword and positional argument support. Works like a normal class - you can override just about anything in the
subclass (eg: a custom ``__init__``). In contrast, `hynek/characteristic`_
forces different call schematics and calls your ``__init__`` with different arguments.
-----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-fields
Version : 5.0.0-4.6
Arch : noarch
Vendor : openSUSE
Installed Size : 111.9 KiB
Installed : No
Status : not installed
Source package : python-fields-5.0.0-4.6.src
Upstream URL : https://github.com/ionelmc/python-fields
Summary : Container class boilerplate killer
Description :
Container class boilerplate killer.
Features:
* Human-readable ``__repr__``
* Complete set of comparison methods
* Keyword and positional argument support. Works like a normal class - you can override just about anything in the
subclass (eg: a custom ``__init__``). In contrast, `hynek/characteristic
forces different call schematics and calls your ``__init__`` with different arguments.