Python Build Reasonableness
Go to file
Jeremy Stanley 538d2c21a1 Support Description-Content-Type metadata
As of setuptools 36.4.0, support for Description-Content-Type
metadata was added via the long_description_content_type variable.
Add a metadata.description-content-type option for setup.cfg so it
can be provided through PBR. This makes it possible to instruct PyPI
and potentially other frontends to know an explicit RFC 1341 content
type, along with character set and variant, for the accompanying
long description.

Change-Id: I852f603d9ca4e4cd469eab4cae9933ef2581e3af
2017-12-04 19:46:41 +00:00
doc/source Support Description-Content-Type metadata 2017-12-04 19:46:41 +00:00
pbr Support Description-Content-Type metadata 2017-12-04 19:46:41 +00:00
releasenotes Remove setting of version/release from releasenotes 2017-11-16 18:54:23 +01:00
tools Add reno for release notes management 2017-10-10 09:36:59 +01:00
.coveragerc Update .coveragerc after the removal of openstack directory 2016-10-19 15:16:29 +05:30
.gitignore Add reno for release notes management 2017-10-10 09:36:59 +01: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 Update URLs in documents according to document migration 2017-07-13 12:16:24 +08:00
setup.cfg Support Description-Content-Type metadata 2017-12-04 19:46:41 +00:00
setup.py Move d2to1 more into the source tree 2013-07-21 10:20:03 -07:00
test-requirements.txt Updated from global requirements 2017-11-16 11:02:49 +00:00
tox.ini Add reno for release notes management 2017-10-10 09:36:59 +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.