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 9257b68435 Merge "Switch to Ussuri jobs" 2 months ago
doc Stop using pbr sphinx integration 8 months ago
pbr trivial: Use 'open' context manager 5 months ago
playbooks/legacy Remove neutron-lbaas 9 months ago
releasenotes option to print only the version of a package 8 months ago
tools Install more dependencies for integration testing 9 months ago
.coveragerc Update .coveragerc after the removal of openstack directory 3 years ago
.gitignore Switch to stestr 1 year ago
.gitreview OpenDev Migration Patch 10 months ago
.mailmap Clean up hacking and path issues with d2to1 6 years ago
.stestr.conf Switch to stestr 1 year ago
.zuul.yaml Switch to Ussuri jobs 2 months ago
CONTRIBUTING.rst Workflow documentation is now in infra-manual 5 years ago
LICENSE Split out oslo.packaging. 7 years ago
README.rst Update URLs in documents according to document migration 2 years ago
lower-constraints.txt Stop using pbr sphinx integration 8 months ago
setup.cfg Resolve some issue with tox.ini, setup.cfg 8 months ago trivial: Fix file permissions 1 year ago
test-requirements.txt Update to latest hacking 5 months ago
tox.ini Update to latest hacking 5 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.