Python Build Reasonableness
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul 8cd1a06e82 Merge "Allow PEP517 without setup_requires" 4 weeks ago
doc Clarify the need for with PEP517 4 weeks ago
pbr Allow PEP517 without setup_requires 4 weeks ago
playbooks/pbr-installation-openstack Cleanup old legacy devstack-gate jobs 1 year ago
releasenotes Add a PEP517 interface 1 month ago
tools Increase OS_TEST_TIMEOUT to 1200 8 months ago
.coveragerc Update .coveragerc after the removal of openstack directory 5 years ago
.gitignore Add Release Notes to documentation 1 year ago
.gitreview OpenDev Migration Patch 3 years ago
.mailmap Clean up hacking and path issues with d2to1 9 years ago
.pre-commit-config.yaml Move flake8 as a pre-commit local target. 8 months ago
.stestr.conf Switch to stestr 3 years ago
.zuul.yaml Add python2 testing back to PBR 4 weeks ago
CONTRIBUTING.rst Update some url to use 1 year ago
LICENSE Split out oslo.packaging. 9 years ago
README.rst Add Release Notes to documentation 1 year ago
pyproject.toml.future Add a PEP517 interface 1 month ago
setup.cfg Update some url to use 1 year ago trivial: Fix file permissions 3 years ago
test-requirements.txt Update dependencies to avoid failure with old pip 8 months ago
tox.ini Dropping lower constraints testing 9 months ago



Latest Version


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.