How to Install and Uninstall python3-werkzeug.noarch Package on CentOS Stream 9

Last updated: September 24,2024

1. Install "python3-werkzeug.noarch" package

This guide covers the steps necessary to install python3-werkzeug.noarch on CentOS Stream 9


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                python3-werkzeug.noarch
            
                    
    
    Copied

2. Uninstall "python3-werkzeug.noarch" package

Please follow the instructions below to uninstall python3-werkzeug.noarch on CentOS Stream 9:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                python3-werkzeug.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the python3-werkzeug.noarch package on CentOS Stream 9

Last metadata expiration check: 0:39:42 ago on Sat Mar 16 16:03:45 2024.
Available Packages
Name : python3-werkzeug
Version : 2.0.3
Release : 3.el9.1
Architecture : noarch
Size : 427 k
Source : python-werkzeug-2.0.3-3.el9.1.src.rpm
Repository : epel
Summary : Comprehensive WSGI web application library
URL : https://werkzeug.palletsprojects.com
License : BSD
Description : Werkzeug
: ========
:
: 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.).