beaker 1.10.0-1 source package in Ubuntu
Changelog
beaker (1.10.0-1) unstable; urgency=medium [ Ondřej Nový ] * d/control: Remove ancient X-Python-Version field * Convert git repository from git-dpm to gbp layout [ Piotr Ożarowski ] * New upstream release -- Piotr Ożarowski <email address hidden> Sun, 30 Dec 2018 15:30:47 +0100
Upload details
- Uploaded by:
- Debian Python Modules Team
- Uploaded to:
- Sid
- Original maintainer:
- Debian Python Modules Team
- Architectures:
- all
- Section:
- web
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
beaker_1.10.0-1.dsc | 2.4 KiB | a656ce7ae7b7dd00804e752e0da32a557503b98367b47dd60be348df81fce862 |
beaker_1.10.0.orig.tar.gz | 40.1 KiB | 6072892918225f5a055413082f2ff285f3ebca6a3873a0d6e163253ba83f0450 |
beaker_1.10.0-1.debian.tar.xz | 5.4 KiB | 39e0376845699be56ffe327bddbeb96c7d4dcc147699b72747a2acfd6ad93cc4 |
Available diffs
- diff from 1.9.1-1 to 1.10.0-1 (3.0 KiB)
No changes file available.
Binary packages built by this source
- python-beaker: No summary available for python-beaker in ubuntu focal.
No description available for python-beaker in ubuntu focal.
- python3-beaker: cache and session library for Python 3
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.
.
Features:
* 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 cookies to prevent session hijacking/spoofing
* Cookie-only sessions to remove the need for a database or file backend
(ideal for clustered systems)
* Extensible Container object to support new back-ends
* Caches 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