pbr
Python Build Reasonableness
Decision gist · record as of 2026-08-14
Yes, if you are maintaining OpenStack projects or multi-project ecosystems where consistent, declarative build configuration saves effort across many repositories. Yes-with-conditions if you are starting a new project: PBR's aging maintenance (284 days since release) and focus on backward compatibility over innovation mean it may not track the latest Python packaging standards as closely as actively maintained alternatives. No if you need cutting-edge support for modern packaging standards or are building a single, simple package where setuptools alone suffices.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires setuptools as a runtime dependency; designed to work with setup.py or setup.cfg declarative configuration.
- Low install friction with a single runtime dependency on setuptools.
- Maintenance status is aging (284 days since last release), but the package is marked Production/Stable and has been actively maintained since 2013.
License · maintenance · safety
Apache-2.0 (permissive) — Licensed under Apache License 2.0 (permissive), allowing free use, modification, and distribution with minimal restrictions—suitable for both open-source and commercial projects.
last release 2025-11-03 (284 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 30,666,742 downloads/mo, #794 on PyPI
Alternatives
Verify before relying
pip install pbr
# In setup.py:
from setuptools import setup
setup(setup_requires=['pbr'], pbr=True)- Whether the 284-day release gap reflects active maintenance or dormancy relative to setuptools evolution.
- Current compatibility with modern Python packaging standards (PEP 517, pyproject.toml) beyond what the description claims.
What it is and what it does
PBR is a setuptools wrapper that automates common packaging tasks by applying sensible defaults to your build process. It originated from shared code patterns across OpenStack projects and has evolved into a general-purpose tool for reducing boilerplate in Python package setup. Rather than requiring extensive manual configuration, PBR reads from setup.cfg or pyproject.toml and handles versioning, changelog generation, and other repetitive setup steps automatically.
The package is built on declarative configuration principles, tracing its lineage through d2to1 and distutils2 concepts. It aims to provide a stable, backward-compatible foundation for packaging—deliberately limiting feature removals to ensure older projects continue to install cleanly with recent PBR versions. It supports Python 2.7 and Python 3.5 through 3.11, though its aging maintenance status suggests it may not track the latest packaging innovations as quickly as newer tools.
Use it for
- Automate version management and changelog generation for OpenStack or similar multi-project ecosystems.
- Simplify setup.py by moving configuration to declarative setup.cfg files with sensible PBR defaults.
- Ensure long-tail compatibility: install older projects without manual version pinning of build dependencies.
- Reduce boilerplate in package setup across multiple related projects by applying consistent defaults.
- Migrate from distutils to modern setuptools with minimal code changes using declarative config support.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are maintaining OpenStack projects or multi-project ecosystems where consistent, declarative build configuration saves effort across many repositories.
Yes-with-conditions if you are starting a new project: PBR's aging maintenance (284 days since release) and focus on backward compatibility over innovation mean it may not track the latest Python packaging standards as closely as actively maintained alternatives. No if you need cutting-edge support for modern packaging standards or are building a single, simple package where setuptools alone suffices.
Install
pbr on PyPI
Before you install
Low install friction with a single runtime dependency on setuptools. Maintenance status is aging (284 days since last release), but the package is marked Production/Stable and has been actively maintained since 2013.
Requires setuptools as a runtime dependency; designed to work with setup.py or setup.cfg declarative configuration.
License in practice
Licensed under Apache License 2.0 (permissive), allowing free use, modification, and distribution with minimal restrictions—suitable for both open-source and commercial projects.
Quickstart
pip install pbr
# In setup.py:
from setuptools import setup
setup(setup_requires=['pbr'], pbr=True)Verify before relying
- Whether the 284-day release gap reflects active maintenance or dormancy relative to setuptools evolution.
- Current compatibility with modern Python packaging standards (PEP 517, pyproject.toml) beyond what the description claims.
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release >=2.6 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagesetuptools |
| Maintenance | Aging 284 days since the last release |
| First released | |
| Downloads | 30,666,742 / month, #794 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableEnvironment :: ConsoleEnvironment :: OpenStackIntended Audience :: DevelopersIntended Audience :: Information TechnologyOperating System :: OS IndependentProgramming Language :: PythonProgramming Language :: Python :: 2Programming Language :: Python :: 2.7Programming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.5Programming Language :: Python :: 3.6Programming Language :: Python :: 3.7Programming Language :: Python :: 3.8Programming Language :: Python :: 3.9 |
Evidence: pbr-7.0.3-py2.py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “python package build defaults”
- pbrPBR injects sensible defaults into setuptools to simplify Python…
- colcon-defaultsExtends colcon to load default command-line argument values from a…
- django-appconfProvides a base class for Django apps to define and manage…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also oslo.log · oslo.config · coherent.licensed · setuptools-protobuf · panda3d-simplepbr · versioneer-518 · setuptools-git-versioning · versioneer · neutron-lib · setuptools-odoo