openstack
/
pbr
Code Issues Proposed changes
Python Build Reasonableness
777 Commits 2 Branches 105 Tags 10 MiB
Python 98%
Shell 1.7%
C 0.3%
Go to file
Elena Ezhova b72e4467e1 Remove self.pre_run calls in packaging.py 
pre_run was a method of _PipInstallTestRequires class which was
removed by https://review.openstack.org/#/c/181785/.

Change-Id: I2118f2a96d0c9984797424e5dda47547c8e24621
Closes-Bug: #1456663
 		2015-05-20 00:01:07 +03:00
doc/source Merge "Teach pbr to read extras and env markers" 2015-05-15 13:12:41 +00:00
pbr Remove self.pre_run calls in packaging.py 2015-05-20 00:01:07 +03:00
tools Bump integration test timeouts. 2015-05-14 19:35:50 +12:00
.gitignore Add vim and emacs files to .gitignore. 2013-05-30 02:04:43 -04:00
.gitreview Rename back to PBR. 2013-03-17 23:27:50 -07:00
.mailmap Clean up hacking and path issues with d2to1 2013-07-11 15:02:12 -04:00
.testr.conf Parallelise integration tests. 2015-05-02 09:05:54 +12: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
MANIFEST.in Add missing files to the tarball. 2013-05-10 18:41:52 +00:00
README.rst Update README format to match release notes tool 2015-01-27 14:39:00 -05:00
setup.cfg Advertise support for Python3.4 2015-05-08 16:06:45 -04:00
setup.py Move d2to1 more into the source tree 2013-07-21 10:20:03 -07:00
test-requirements.txt Update hacking to 0.10.x series 2015-05-19 09:41:49 -07:00
tox.ini Finish removing invocations of pip. 2015-05-12 09:31:20 +12:00

README.rst

Introduction

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.