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 5edde7db82 Merge "Begin work to modernize pbr's integration testing" 11 hours ago
doc Merge "Re-add ChangeLog" 4 days ago
pbr Update some url to use opendev.org 4 days ago
playbooks Begin work to modernize pbr's integration testing 4 days ago
releasenotes Support newer openstackdocstheme 4 days ago
tools Begin work to modernize pbr's integration testing 4 days ago
.coveragerc Update .coveragerc after the removal of openstack directory 3 years ago
.gitignore Switch to stestr 2 years ago
.gitreview OpenDev Migration Patch 1 year ago
.mailmap Clean up hacking and path issues with d2to1 7 years ago
.stestr.conf Switch to stestr 2 years ago
.zuul.yaml Begin work to modernize pbr's integration testing 4 days ago
CONTRIBUTING.rst Update some url to use opendev.org 4 days ago
LICENSE Split out oslo.packaging. 7 years ago
README.rst Re-add ChangeLog 4 days ago
lower-constraints.txt Add support for virtualenv 20.x 5 days ago
setup.cfg Update some url to use opendev.org 4 days ago
setup.py trivial: Fix file permissions 2 years ago
test-requirements.txt Update hacking 5 days ago
tox.ini Re-add ChangeLog 4 days 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.