How to Install and Uninstall python39-ZConfig Package on openSuSE Tumbleweed

Last updated: December 25,2024

1. Install "python39-ZConfig" package

Please follow the instructions below to install python39-ZConfig on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python39-ZConfig
            
                    
    
    Copied

2. Uninstall "python39-ZConfig" package

This tutorial shows how to uninstall python39-ZConfig on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python39-ZConfig
            
                    
    
    Copied

3. Information about the python39-ZConfig package on openSuSE Tumbleweed

Information for package python39-ZConfig:
-----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python39-ZConfig
Version : 4.0-1.2
Arch : noarch
Vendor : openSUSE
Installed Size : 845.1 KiB
Installed : No
Status : not installed
Source package : python-ZConfig-4.0-1.2.src
Upstream URL : https://github.com/zopefoundation/ZConfig
Summary : Structured Configuration Library
Description :
ZConfig is a configuration library intended for general use. It supports a
hierarchical schema-driven configuration model that allows a schema to specify
data conversion routines written in Python. ZConfig's model is very different
from the model supported by the ConfigParser module found in Python's standard
library, and is more suitable to configuration-intensive applications.
ZConfig schema are written in an XML-based language and are able to "import"
schema components provided by Python packages. Since components are able to
bind to conversion functions provided by Python code in the package (or
elsewhere), configuration objects can be arbitrarily complex, with values that
have been verified against arbitrary constraints. This makes it easy for
applications to separate configuration support from configuration loading even
with configuration data being defined and consumed by a wide range of separate
packages.