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
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
|
Source: python-pbr
Section: python
Priority: optional
Maintainer: PKG OpenStack <openstack-devel@lists.alioth.debian.org>
Uploaders: Thomas Goirand <zigo@debian.org>,
Prach Pongpanich <prachpub@gmail.com>,
Build-Depends: debhelper (>= 9),
dh-python,
git,
gnupg,
openstack-pkg-tools (>= 52~),
python-all,
python-all-dev,
python-setuptools,
python-sphinx,
python3-all,
python3-all-dev,
python3-setuptools,
python3-sphinx,
Build-Depends-Indep: python-coverage,
python-fixtures (>= 1.3.1),
python-markupsafe,
python-mock (>= 1.3),
python-pip,
python-six (>= 1.9.0),
python-testresources,
python-testscenarios,
python-testtools (>= 1.4.0),
python-virtualenv,
python-wheel,
python3-fixtures (>= 0.3.14),
python3-markupsafe,
python3-mock (>= 1.3),
python3-pip,
python3-six (>= 1.9.0),
python3-testresources,
python3-testscenarios,
python3-testtools (>= 1.4.0),
python3-virtualenv,
python3-wheel,
subunit (>= 1.1.0),
testrepository,
Standards-Version: 3.9.8
Vcs-Browser: https://git.openstack.org/cgit/openstack/deb-python-pbr
Vcs-Git: https://git.openstack.org/openstack/deb-python-pbr
Homepage: https://pypi.python.org/pypi/pbr
XS-Testsuite: autopkgtest
Package: python-pbr
Architecture: all
Depends: python-pkg-resources,
python-six (>= 1.9.0),
${misc:Depends},
${python:Depends},
Recommends: ${python:Recommends},
Description: inject useful and sensible default behaviors into setuptools - Python 2.x
PBR (Python Build Reasonableness) is a library that injects some useful and
sensible default behaviors into your setuptools run. PBR can:
* Manage version number based on git revisions and tags (Version file).
* Generate AUTHORS file from git log
* Generate ChangeLog from git log
* Generate Sphinx autodoc stub files for your whole module
* Store your dependencies in a pip requirements file
* Use your README file as a long_description
* Smartly find packages under your root package
.
PBR is only mildly configurable. The basic idea is that there's a decent way
to run things and if you do, you should reap the rewards, because then it's
simple and repeatable. If you want to do things differently, cool! But you've
already got the power of Python at your fingertips, so you don't really need
PBR.
.
PBR builds on top of the work that d2to1 started to provide for declarative
configuration. d2to1 is itself an implementation of the ideas behind
distutils2. Although distutils2 is now abandoned in favor of work towards PEP
426 and Metadata 2.0, declarative config is still a great idea and
specifically important in trying to distribute setup code as a library when
that library itself will alter how the setup is processed. As Metadata 2.0 and
other modern Python packaging PEPs come out, PBR aims to support them as
quickly as possible.
.
This package provides support for Python 2.x.
Package: python3-pbr
Architecture: all
Depends: python3-pkg-resources,
python3-six (>= 1.9.0),
${misc:Depends},
${python3:Depends},
Recommends: ${python3:Recommends},
Description: inject useful and sensible default behaviors into setuptools - Python 3.x
PBR (Python Build Reasonableness) is a library that injects some useful and
sensible default behaviors into your setuptools run. PBR can:
* Manage version number based on git revisions and tags (Version file).
* Generate AUTHORS file from git log
* Generate ChangeLog from git log
* Generate Sphinx autodoc stub files for your whole module
* Store your dependencies in a pip requirements file
* Use your README file as a long_description
* Smartly find packages under your root package
.
PBR is only mildly configurable. The basic idea is that there's a decent way
to run things and if you do, you should reap the rewards, because then it's
simple and repeatable. If you want to do things differently, cool! But you've
already got the power of Python at your fingertips, so you don't really need
PBR.
.
PBR builds on top of the work that d2to1 started to provide for declarative
configuration. d2to1 is itself an implementation of the ideas behind
distutils2. Although distutils2 is now abandoned in favor of work towards PEP
426 and Metadata 2.0, declarative config is still a great idea and
specifically important in trying to distribute setup code as a library when
that library itself will alter how the setup is processed. As Metadata 2.0 and
other modern Python packaging PEPs come out, PBR aims to support them as
quickly as possible.
.
This package provides support for Python 3.x.
Package: python-pbr-doc
Section: doc
Architecture: all
Depends: ${misc:Depends},
${sphinxdoc:Depends},
Description: inject useful and sensible default behaviors into setuptools - doc
PBR (Python Build Reasonableness) is a library that injects some useful and
sensible default behaviors into your setuptools run. PBR can:
* Manage version number based on git revisions and tags (Version file).
* Generate AUTHORS file from git log
* Generate ChangeLog from git log
* Generate Sphinx autodoc stub files for your whole module
* Store your dependencies in a pip requirements file
* Use your README file as a long_description
* Smartly find packages under your root package
.
PBR is only mildly configurable. The basic idea is that there's a decent way
to run things and if you do, you should reap the rewards, because then it's
simple and repeatable. If you want to do things differently, cool! But you've
already got the power of Python at your fingertips, so you don't really need
PBR.
.
PBR builds on top of the work that d2to1 started to provide for declarative
configuration. d2to1 is itself an implementation of the ideas behind
distutils2. Although distutils2 is now abandoned in favor of work towards PEP
426 and Metadata 2.0, declarative config is still a great idea and
specifically important in trying to distribute setup code as a library when
that library itself will alter how the setup is processed. As Metadata 2.0 and
other modern Python packaging PEPs come out, PBR aims to support them as
quickly as possible.
.
This package provides the documentation.
|
