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 45d4c9f02f Merge "Fix symbol identification in multiline message" 4 months ago
doc Drop wheel from pyproject.toml examples 9 months ago
pbr Merge "Fix symbol identification in multiline message" 4 months ago
playbooks/pbr-installation-openstack Cleanup old legacy devstack-gate jobs 2 years ago
releasenotes Fix symbol identification in multiline message 4 months ago
tools Increase OS_TEST_TIMEOUT to 1200 2 years ago
.coveragerc Update .coveragerc after the removal of openstack directory 6 years ago
.gitignore Add Release Notes to documentation 2 years ago
.gitreview OpenDev Migration Patch 4 years ago
.mailmap Clean up hacking and path issues with d2to1 10 years ago
.pre-commit-config.yaml Upgrade the pre-commit-hooks version 2 years ago
.stestr.conf Switch to stestr 4 years ago
.zuul.yaml Add python2 testing back to PBR 1 year ago
CONTRIBUTING.rst Specify Changelog procedure 6 months ago
LICENSE Split out oslo.packaging. 10 years ago
README.rst Add Release Notes to documentation 2 years ago
pyproject.toml.future Future-proofing pyproject.toml 8 months ago
setup.cfg Adding python classifiers py38 & py39 7 months ago
setup.py trivial: Fix file permissions 4 years ago
test-requirements.txt remove explicit mock 10 months ago
tox.ini Changed minversion in tox to 3.18.0. 10 months ago

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.