How to Install and Uninstall python311-plaster Package on openSuSE Tumbleweed
Last updated: November 08,2024
1. Install "python311-plaster" package
This guide let you learn how to install python311-plaster on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python311-plaster
Copied
2. Uninstall "python311-plaster" package
This guide let you learn how to uninstall python311-plaster on openSuSE Tumbleweed:
$
sudo zypper remove
python311-plaster
Copied
3. Information about the python311-plaster package on openSuSE Tumbleweed
Information for package python311-plaster:
------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python311-plaster
Version : 1.1.2-2.6
Arch : noarch
Vendor : openSUSE
Installed Size : 56.6 KiB
Installed : No
Status : not installed
Source package : python-plaster-1.1.2-2.6.src
Upstream URL : http://docs.pylonsproject.org/projects/plaster/en/latest
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 : python311-plaster
Version : 1.1.2-2.6
Arch : noarch
Vendor : openSUSE
Installed Size : 56.6 KiB
Installed : No
Status : not installed
Source package : python-plaster-1.1.2-2.6.src
Upstream URL : http://docs.pylonsproject.org/projects/plaster/en/latest
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.