1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
Source: beaker
Section: python
Priority: optional
Maintainer: Debian Python Team <team+python@tracker.debian.org>
Uploaders: Piotr Ożarowski <piotr@debian.org>
Build-Depends: debhelper-compat (= 13)
Build-Depends-Indep: dh-python, python3-all,
python3-setuptools,
# for tests
python3-sqlalchemy (>= 0.4), python3-webtest,
python3-pycryptodome, python3-pylibmc | python3-memcache,
python3-pymongo,
python3-redis,
Standards-Version: 4.6.1
Homepage: https://beaker.readthedocs.io
Vcs-Git: https://salsa.debian.org/python-team/packages/beaker.git
Vcs-Browser: https://salsa.debian.org/python-team/packages/beaker
Testsuite: autopkgtest-pkg-python
Rules-Requires-Root: no
Package: python3-beaker
Architecture: all
Depends: ${python3:Depends}, ${misc:Depends}
Recommends: ${python3:Recommends}, python3-pkg-resources
Suggests: ${python3:Suggests},
python3-sqlalchemy,
python3-pycryptopp | python3-pycryptodome,
python3-pylibmc | python3-memcache,
python3-pymongo,
python3-redis,
Description: 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
|
