How to Install and Uninstall python2-Beaker Package on openSUSE Leap

Last updated: April 26,2024

Deprecated! Installation of this package may no longer be supported.

1. Install "python2-Beaker" package

Here is a brief guide to show you how to install python2-Beaker on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python2-Beaker
            
                    
    
    Copied

2. Uninstall "python2-Beaker" package

In this section, we are going to explain the necessary steps to uninstall python2-Beaker on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python2-Beaker
            
                    
    
    Copied

3. Information about the python2-Beaker package on openSUSE Leap

Information for package python2-Beaker:
---------------------------------------
Repository : Main Repository
Name : python2-Beaker
Version : 1.11.0-bp153.1.21
Arch : noarch
Vendor : openSUSE
Installed Size : 440,1 KiB
Installed : No
Status : not installed
Source package : python-Beaker-1.11.0-bp153.1.21.src
Summary : A Session and Caching library with WSGI Middleware
Description :
Beaker is a web session and general caching library that includes WSGI
middleware for use in web applications.
As a general caching library, Beaker can handle storing for various times
any Python object that can be pickled with optional back-ends on a
fine-grained basis.
Beaker was built largely on the code from MyghtyUtils, then refactored and
extended with database support.
Beaker includes Cache and Session WSGI middleware to ease integration with
WSGI capable frameworks, and is automatically used by Pylons.
Features include:
* Fast, robust performance
* Multiple reader/single writer lock system to avoid duplicate simultaneous
cache creation
* Cache back-ends include dbm, file, memory, memcached, and database (Using
SQLAlchemy for multiple-db vendor support)
* Signed cookie's to prevent session hijacking/spoofing
* Cookie-only sessions to remove the need for a db or file backend (ideal
for clustered systems)
* Extensible Container object to support new back-ends
* Cache's can be divided into namespaces (to represent templates, objects,
etc.) then keyed for different copies
* Create functions for automatic call-backs to create new cache copies after
expiration
* Fine-grained toggling of back-ends, keys, and expiration per Cache object