File: control

package info (click to toggle)
python-dogpile.cache 0.6.2-6
  • links: PTS, VCS
  • area: main
  • in suites: buster, sid
  • size: 596 kB
  • sloc: python: 3,663; makefile: 100; sh: 3
file content (122 lines) | stat: -rw-r--r-- 4,348 bytes parent folder | download
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
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
Source: python-dogpile.cache
Section: python
Priority: optional
Maintainer: Debian OpenStack <team+openstack@tracker.debian.org>
Uploaders:
 Thomas Goirand <zigo@debian.org>,
Build-Depends:
 debhelper (>= 9),
 dh-python,
 openstack-pkg-tools (>= 52~),
 python-all,
 python-setuptools,
 python-sphinx,
 python3-all,
 python3-setuptools,
Build-Depends-Indep:
 python-changelog,
 python-coverage,
 python-mako,
 python-mock,
 python-pytest,
 python-sphinx-paramlinks,
 python3-coverage,
 python3-mako,
 python3-mock,
 python3-pytest,
Standards-Version: 3.9.8
Vcs-Browser: https://salsa.debian.org/openstack-team/python/python-dogpile.cache
Vcs-Git: https://salsa.debian.org/openstack-team/python/python-dogpile.cache.git
Homepage: https://bitbucket.org/zzzeek/dogpile.cache

Package: python-dogpile.cache
Architecture: all
Depends:
 ${misc:Depends},
 ${python:Depends},
Recommends:
 ${python:Recommends},
Breaks:
 python-dogpile.core (<< 0.6.1-1~),
Replaces:
 python-dogpile.core (<< 0.6.1-1~),
Description: caching front-end based on the Dogpile lock - Python 2.x
 A caching API built around the concept of a "dogpile lock", which allows
 continued access to an expiring data value while a single thread generates a
 new value.
 .
 dogpile.cache builds on the dogpile.core locking system
 (see http://pypi.python.org/pypi/dogpile.core), which implements the idea of
 "allow one creator to write while others read" in the abstract. Overall,
 dogpile.cache is intended as a replacement to the Beaker (see
 http://beaker.groovie.org) caching system, the internals of which are written
 by the same author. All the ideas of Beaker which "work" are re-implemented in
 dogpile.cache in a more efficient and succinct manner, and all the cruft
 (Beaker's internals were first written in 2005) relegated to the trash heap.
 .
 This package provides the Python 2.x module.

Package: python-dogpile.cache-doc
Section: doc
Architecture: all
Depends:
 ${misc:Depends},
 ${sphinxdoc:Depends},
Description: caching front-end based on the Dogpile lock - doc
 A caching API built around the concept of a "dogpile lock", which allows
 continued access to an expiring data value while a single thread generates a
 new value.
 .
 dogpile.cache builds on the dogpile.core locking system
 (see http://pypi.python.org/pypi/dogpile.core), which implements the idea of
 "allow one creator to write while others read" in the abstract. Overall,
 dogpile.cache is intended as a replacement to the Beaker (see
 http://beaker.groovie.org) caching system, the internals of which are written
 by the same author. All the ideas of Beaker which "work" are re-implemented in
 dogpile.cache in a more efficient and succinct manner, and all the cruft
 (Beaker's internals were first written in 2005) relegated to the trash heap.
 .
 This package provides the documentation.

Package: python-dogpile.core
Architecture: all
Depends:
 python-dogpile.cache,
 ${misc:Depends},
Description: transitional dummy package for python-dogpile.core
 This transitional package is safe to remove.

Package: python3-dogpile.cache
Architecture: all
Depends:
 ${misc:Depends},
 ${python3:Depends},
Recommends:
 ${python:Recommends},
Breaks:
 python3-dogpile.core (<< 0.6.1-1~),
Replaces:
 python3-dogpile.core (<< 0.6.1-1~),
Description: caching front-end based on the Dogpile lock - Python 3.x
 A caching API built around the concept of a "dogpile lock", which allows
 continued access to an expiring data value while a single thread generates a
 new value.
 .
 dogpile.cache builds on the dogpile.core locking system
 (see http://pypi.python.org/pypi/dogpile.core), which implements the idea of
 "allow one creator to write while others read" in the abstract. Overall,
 dogpile.cache is intended as a replacement to the Beaker (see
 http://beaker.groovie.org) caching system, the internals of which are written
 by the same author. All the ideas of Beaker which "work" are re-implemented in
 dogpile.cache in a more efficient and succinct manner, and all the cruft
 (Beaker's internals were first written in 2005) relegated to the trash heap.
 .
 This package provides the Python 3.x module.

Package: python3-dogpile.core
Architecture: all
Depends:
 python3-dogpile.cache,
 ${misc:Depends},
Description: transitional dummy package for python3-dogpile.core
 This transitional package is safe to remove.