beaker 1.11.0-3 source package in Ubuntu

Changelog

beaker (1.11.0-3) unstable; urgency=medium

  * Team upload.
  * Fix autopkgtest tests to depend on python3-all before iterating over all
    supported interpreters (Closes: #1024857).
  * Add Rules-Requires-Root: no.

 -- Stuart Prescott <email address hidden>  Wed, 30 Nov 2022 00:08:43 +1100

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
Lunar release universe web

Builds

Lunar: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
beaker_1.11.0-3.dsc 2.2 KiB 7d6c237f71cf4ddeb97986f90f46a609492605fbeb150a6234582118031ec3ba
beaker_1.11.0.orig.tar.gz 40.0 KiB ad5d1c05027ee3be3a482ea39f8cb70339b41e5d6ace0cb861382754076d187e
beaker_1.11.0-3.debian.tar.xz 7.5 KiB 7c0b335968da2f7f6cff856ba5d9c90651ed57d1290d0ea65eca373f5b192012

Available diffs

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