Python Build Reasonableness
Go to file
Dr. Jens Harbott 46ff9dd967 Add openstack-tox-py312 as non-voting job
Let's start to test with python 3.12.

Change-Id: Ib0e47928d82e6ac57353315c5e2341e354b42d59
2024-05-28 08:59:40 -07:00
doc Add support for PEP-660 2023-11-01 12:53:18 -07:00
pbr Add SetupTools to our functional testing venvs 2024-05-28 08:59:40 -07:00
playbooks/pbr-installation-openstack Cleanup old legacy devstack-gate jobs 2020-08-06 10:41:29 -07:00
releasenotes Add release note for build_sphinx removal 2023-06-01 08:24:37 -07:00
tools Remove numpy dependencies 2023-01-06 14:36:51 +00: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 Upgrade the pre-commit-hooks version 2021-05-18 11:17:07 +08:00
.stestr.conf Switch to stestr 2018-07-18 10:12:17 +01:00
.zuul.yaml Add openstack-tox-py312 as non-voting job 2024-05-28 08:59:40 -07:00
CONTRIBUTING.rst Specify Changelog procedure 2022-06-13 17:06:43 -04: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 support for PEP-660 2023-11-01 12:53:18 -07:00
setup.cfg Merge "Use summary for the package summary" 2024-01-30 12:50:25 +00:00 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 Use SetupTools' vendored distutils in tests 2024-05-28 08:59:40 -07:00



Latest Version


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.