How to Install and Uninstall python312-parse_type Package on openSuSE Tumbleweed
Last updated: November 24,2024
1. Install "python312-parse_type" package
In this section, we are going to explain the necessary steps to install python312-parse_type on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python312-parse_type
Copied
2. Uninstall "python312-parse_type" package
Please follow the instructions below to uninstall python312-parse_type on openSuSE Tumbleweed:
$
sudo zypper remove
python312-parse_type
Copied
3. Information about the python312-parse_type package on openSuSE Tumbleweed
Information for package python312-parse_type:
---------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-parse_type
Version : 0.6.2-1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 120.5 KiB
Installed : No
Status : not installed
Source package : python-parse_type-0.6.2-1.4.src
Upstream URL : https://github.com/jenisys/parse_type
Summary : Extension to the parse module
Description :
parse_type extends the parse module (opposite of string.format()) with
the following features:
* build type converters for common use cases (enum/mapping, choice)
* build a type converter with a cardinality constraint (0..1, 0..*, 1..*)
from the type converter with cardinality=1.
* compose a type converter from other type converters
* an extended parser that supports the CardinalityField naming schema
and creates missing type variants (0..1, 0..*, 1..*) from the
primary type converter
---------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-parse_type
Version : 0.6.2-1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 120.5 KiB
Installed : No
Status : not installed
Source package : python-parse_type-0.6.2-1.4.src
Upstream URL : https://github.com/jenisys/parse_type
Summary : Extension to the parse module
Description :
parse_type extends the parse module (opposite of string.format()) with
the following features:
* build type converters for common use cases (enum/mapping, choice)
* build a type converter with a cardinality constraint (0..1, 0..*, 1..*)
from the type converter with cardinality=1.
* compose a type converter from other type converters
* an extended parser that supports the CardinalityField naming schema
and creates missing type variants (0..1, 0..*, 1..*) from the
primary type converter