Ubuntu
beaker package

beaker 1.12.1-3 source package in Ubuntu

Changelog

beaker (1.12.1-3) unstable; urgency=medium

  * Team upload.
  * Reorder sequence of d/control fields by cme (routine-update)
  * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
  * Use nocheck profile instead of comment
  * Versioned Build-Depends: python3-pycryptodome (>= 3.20)
    Closes: #1058366
  * Drop python3-pycryptopp from alternatives since this was removed
    from Debian

 -- Andreas Tille <email address hidden>  Wed, 07 Feb 2024 19:06:02 +0100

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
Oracular release universe web
Noble release universe web

Builds

Noble: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
beaker_1.12.1-3.dsc 2.2 KiB 7fb9e4e704f419cbd1b7b9ced90936aec5e100ee471facdc5ebf61a0e91b002a
beaker_1.12.1.orig.tar.gz 86.9 KiB 135c41ce48a7f994c15abe050949e6ce70f3e164f0dc81ceb56c4d9e3106b9f2
beaker_1.12.1-3.debian.tar.xz 6.5 KiB b8e3ab97ec1e15aec779aad430172b5b20fd8e3cd889d26cdaba583372387815

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