How to Install and Uninstall python311-Werkzeug Package on openSuSE Tumbleweed

Last updated: October 06,2024

1. Install "python311-Werkzeug" package

In this section, we are going to explain the necessary steps to install python311-Werkzeug on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python311-Werkzeug
            
                    
    
    Copied

2. Uninstall "python311-Werkzeug" package

In this section, we are going to explain the necessary steps to uninstall python311-Werkzeug on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python311-Werkzeug
            
                    
    
    Copied

3. Information about the python311-Werkzeug package on openSuSE Tumbleweed

Information for package python311-Werkzeug:
-------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python311-Werkzeug
Version : 3.0.1-1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 1.9 MiB
Installed : No
Status : not installed
Source package : python-Werkzeug-3.0.1-1.4.src
Upstream URL : https://werkzeug.palletsprojects.com
Summary : The Swiss Army knife of Python web development
Description :
Werkzeug started as simple collection of various utilities for WSGI
applications and has become one of the most advanced WSGI utility
modules. It includes a powerful debugger, full featured request and
response objects, HTTP utilities to handle entity tags, cache control
headers, HTTP dates, cookie handling, file uploads, a powerful URL
routing system and a bunch of community contributed addon modules.
Werkzeug is unicode aware and doesn't enforce a specific template
engine, database adapter or anything else. It doesn't even enforce
a specific way of handling requests and leaves all that up to the
developer. It's most useful for end user applications which should work
on as many server environments as possible (such as blogs, wikis,
bulletin boards, etc.).