openstack
/
pbr
Code Issues Proposed changes
Python Build Reasonableness
901 Commits 2 Branches 105 Tags 10 MiB
Python 98%
Shell 1.7%
C 0.3%
Go to file
Ian Wienand 87288ccfd8 Move to oslosphinx 
I noticed the current API documentation is unreadable [1].  Remove the
inbuilt theme and move to oslosphinx for module/api documentation.

[1] http://docs.openstack.org/developer/pbr/api/pbr.version.html

Change-Id: I8d92d849b8a2ab4baca960ae8c271214d3c2b8f4
 		2016-06-22 13:18:59 +10:00
doc/source Move to oslosphinx 2016-06-22 13:18:59 +10:00
pbr Move to oslosphinx 2016-06-22 13:18:59 +10:00
tools Use apt-cache generated packages to provide build deps 2016-03-08 14:56:38 +11:00
.coveragerc Add standard code coverage configuration file 2015-10-05 13:18:37 -04:00
.gitignore Move to oslosphinx 2016-06-22 13:18:59 +10: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
README.rst Add shields.io version/downloads links/badges into README.rst 2015-09-24 20:49:31 -04:00
setup.cfg Move to oslosphinx 2016-06-22 13:18:59 +10:00
setup.py Move d2to1 more into the source tree 2013-07-21 10:20:03 -07:00
test-requirements.txt Move to oslosphinx 2016-06-22 13:18:59 +10:00
tox.ini Deprecated tox -downloadcache option removed 2015-12-11 22:28:39 +01: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.