How to Install and Uninstall python311-fields Package on openSUSE Leap
Last updated: November 23,2024
1. Install "python311-fields" package
Please follow the guidelines below to install python311-fields on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
python311-fields
Copied
2. Uninstall "python311-fields" package
Please follow the guidance below to uninstall python311-fields on openSUSE Leap:
$
sudo zypper remove
python311-fields
Copied
3. Information about the python311-fields package on openSUSE Leap
Information for package python311-fields:
-----------------------------------------
Repository : Update repository with updates from SUSE Linux Enterprise 15
Name : python311-fields
Version : 5.0.0-150400.10.3.9
Arch : noarch
Vendor : SUSE LLC
Installed Size : 92.0 KiB
Installed : No
Status : not installed
Source package : python-fields-5.0.0-150400.10.3.9.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 : Update repository with updates from SUSE Linux Enterprise 15
Name : python311-fields
Version : 5.0.0-150400.10.3.9
Arch : noarch
Vendor : SUSE LLC
Installed Size : 92.0 KiB
Installed : No
Status : not installed
Source package : python-fields-5.0.0-150400.10.3.9.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.