Ubuntu
beaker package

beaker 1.12.1-1.1 source package in Ubuntu

Changelog

beaker (1.12.1-1.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Apply patch from Shengjing Zhu to exclude tests relying on running
    redis server. (Closes: #1037035)

 -- Adrian Bunk <email address hidden>  Sat, 05 Aug 2023 20:34:16 +0300

Upload details

Uploaded by:
Debian Python Team
Uploaded to:
Sid
Original maintainer:
Debian Python Team
Architectures:
all
Section:
web
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Mantic release universe web

Builds

Mantic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
beaker_1.12.1-1.1.dsc 2.3 KiB 3564e4f724b1a2fa6a6cb453f2d1a013ede0d87b40afc5305b9e90ef64d869a6
beaker_1.12.1.orig.tar.gz 86.9 KiB 135c41ce48a7f994c15abe050949e6ce70f3e164f0dc81ceb56c4d9e3106b9f2
beaker_1.12.1-1.1.debian.tar.xz 6.5 KiB 010df2007c92b66200749b24a7a1c4ca8cd0fe30a6eadfccbf38a51db9966466

No changes file available.

Binary packages built by this source

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