Python Build Reasonableness
Go to file
Ben Greiner 397b6fcdf9 remove explicit mock
The explicit mock package is not required if you can use unittest.mock
from python >= 3.3

Change-Id: I1e3a764b38be66b994d790768bc5eb9be4237444
2022-01-21 10:44:41 +01:00
doc Clarify the need for setup.py with PEP517 2021-11-08 08:56:18 -08:00
pbr remove explicit mock 2022-01-21 10:44:41 +01:00
playbooks/pbr-installation-openstack Cleanup old legacy devstack-gate jobs 2020-08-06 10:41:29 -07:00
releasenotes Add a PEP517 interface 2021-11-03 10:05:32 -07:00
tools Increase OS_TEST_TIMEOUT to 1200 2021-04-01 11:37:53 +01:00
.coveragerc Update .coveragerc after the removal of openstack directory 2016-10-19 15:16:29 +05:30
.gitignore Add Release Notes to documentation 2020-08-11 21:20:17 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:36:17 +00:00
.mailmap Clean up hacking and path issues with d2to1 2013-07-11 15:02:12 -04:00
.pre-commit-config.yaml Move flake8 as a pre-commit local target. 2021-04-15 12:03:44 +02:00
.stestr.conf Switch to stestr 2018-07-18 10:12:17 +01:00
.zuul.yaml Add python2 testing back to PBR 2021-11-12 10:01:14 -08:00
CONTRIBUTING.rst Update some url to use opendev.org 2020-08-06 15:09:50 +02:00
LICENSE Split out oslo.packaging. 2013-03-10 18:02:43 -04:00
README.rst Add Release Notes to documentation 2020-08-11 21:20:17 +00:00
pyproject.toml.future Add a PEP517 interface 2021-11-03 10:05:32 -07:00
setup.cfg Update some url to use opendev.org 2020-08-06 15:09:50 +02:00
setup.py trivial: Fix file permissions 2018-07-18 10:12:17 +01:00
test-requirements.txt remove explicit mock 2022-01-21 10:44:41 +01:00
tox.ini Don't test with setuptools local distutils 2022-01-20 21:01:47 +00: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.