Python Build Reasonableness
Go to file
Clark Boylan 206b795517 Update hacking
This allows us to run tox -epep8 on newer python versions. Fix the
issues newer hacking calls out. They were complaints about indentation
and ambigious l value variable names.

Change-Id: I9552fba791bdf54649fbe25fc26bffdf8186ff0a
2020-08-05 15:01:21 -07:00
doc Stop using pbr sphinx integration 2019-06-07 18:37:58 +01:00
pbr Update hacking 2020-08-05 15:01:21 -07:00
playbooks/legacy Remove neutron-lbaas 2019-05-23 09:15:38 +00:00
releasenotes option to print only the version of a package 2019-06-24 09:58:26 +00:00
tools Add support for virtualenv 20.x 2020-08-05 15:01:15 -07:00
.coveragerc Update .coveragerc after the removal of openstack directory 2016-10-19 15:16:29 +05:30
.gitignore Switch to stestr 2018-07-18 10:12:17 +01: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
.stestr.conf Switch to stestr 2018-07-18 10:12:17 +01:00
.zuul.yaml Switch to Ussuri jobs 2019-12-03 10:46:48 +08:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:42 +00:00
LICENSE Split out oslo.packaging. 2013-03-10 18:02:43 -04:00
README.rst Update URLs in documents according to document migration 2017-07-13 12:16:24 +08:00
lower-constraints.txt Add support for virtualenv 20.x 2020-08-05 15:01:15 -07:00
setup.cfg Resolve some issue with tox.ini, setup.cfg 2019-06-13 15:46:30 +01:00
setup.py trivial: Fix file permissions 2018-07-18 10:12:17 +01:00
test-requirements.txt Update hacking 2020-08-05 15:01:21 -07:00
tox.ini Add support for virtualenv 20.x 2020-08-05 15:01:15 -07: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.