How to Install and Uninstall python38-plaster Package on openSuSE Tumbleweed
Last updated: December 25,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "python38-plaster" package
Learn how to install python38-plaster on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python38-plaster
Copied
2. Uninstall "python38-plaster" package
Please follow the step by step instructions below to uninstall python38-plaster on openSuSE Tumbleweed:
$
sudo zypper remove
python38-plaster
Copied
3. Information about the python38-plaster package on openSuSE Tumbleweed
Information for package python38-plaster:
-----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python38-plaster
Version : 1.0-2.11
Arch : noarch
Vendor : openSUSE
Installed Size : 56,9 KiB
Installed : No
Status : not installed
Source package : python-plaster-1.0-2.11.src
Summary : A loader interface around multiple config file formats
Description :
Plaster is a loader interface around multiple config file formats.
It exists to define a common API for applications to use when they
wish to load a configuration. The library itself does not aim to
handle anything except a basic API that applications may use to find
and load configuration settings. Any specific constraints should be
implemented in a pluggable loader which can be registered via an
entrypoint.
-----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python38-plaster
Version : 1.0-2.11
Arch : noarch
Vendor : openSUSE
Installed Size : 56,9 KiB
Installed : No
Status : not installed
Source package : python-plaster-1.0-2.11.src
Summary : A loader interface around multiple config file formats
Description :
Plaster is a loader interface around multiple config file formats.
It exists to define a common API for applications to use when they
wish to load a configuration. The library itself does not aim to
handle anything except a basic API that applications may use to find
and load configuration settings. Any specific constraints should be
implemented in a pluggable loader which can be registered via an
entrypoint.