Python Build Reasonableness
Go to file
Stephen Finucane 915e62ef7b trivial: Fix file permissions
No reason for these to be executable.

Change-Id: I9b22f4b9e679a5f618bb3f2a007327bdb0c80305
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
2018-07-18 10:12:17 +01:00
doc/source Add leading 0 on alpha release in semver doc 2018-05-24 14:42:36 +00:00
pbr trivial: Fix file permissions 2018-07-18 10:12:17 +01:00
releasenotes deprecations: Deprecate support for '-py{N}' requirements 2018-01-09 14:31:01 +00:00
tools trivial: Remove 'tools/releasenotes_tox.sh' 2018-07-18 10:12:04 +01:00
.coveragerc Update .coveragerc after the removal of openstack directory 2016-10-19 15:16:29 +05:30
.gitignore Add reno for release notes management 2017-10-10 09:36:59 +01:00
.gitreview Rename back to PBR. 2013-03-17 23:27:50 -07:00
.mailmap Clean up hacking and path issues with d2to1 2013-07-11 15:02:12 -04:00
.testr.conf Parallelise integration tests. 2015-05-02 09:05:54 +12:00
.zuul.yaml add lower-constraints job 2018-03-29 16:07:24 +00:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:42 +00:00
LICENSE Split out oslo.packaging. 2013-03-10 18:02:43 -04:00
README.rst Update URLs in documents according to document migration 2017-07-13 12:16:24 +08:00
lower-constraints.txt add lower-constraints job 2018-03-29 16:07:24 +00:00
setup.cfg Merge "Support PEP 345 Project-URL metadata" 2018-01-08 13:54:33 +00:00
setup.py trivial: Fix file permissions 2018-07-18 10:12:17 +01:00
test-requirements.txt Updated from global requirements 2018-03-15 06:43:31 +00:00
tox.ini trivial: Remove 'tools/releasenotes_tox.sh' 2018-07-18 10:12:04 +01:00

README.rst

Introduction

Latest Version

Downloads

PBR is a library that injects some useful and sensible default behaviors into your setuptools run. It started off life as the chunks of code that were copied between all of the OpenStack projects. Around the time that OpenStack hit 18 different projects each with at least 3 active branches, it seemed like a good time to make that code into a proper reusable library.

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.