python-pbr 5.1.1-0ubuntu3 source package in Ubuntu

Changelog

python-pbr (5.1.1-0ubuntu3) eoan; urgency=medium

  * d/control,d/tests/unit: Drop testing under Python 2 as an interim
    measure to address the fact that python-stestr dropped Python 2
    support during the eoan cycle, but a large number of packages still
    depend on python-pbr.  Python 2 support should be dropped for this
    package during the 'dd' cycle.

 -- James Page <email address hidden>  Tue, 08 Oct 2019 10:24:17 +0100

Upload details

Uploaded by:
James Page
Uploaded to:
Eoan
Original maintainer:
Ubuntu Developers
Architectures:
all
Section:
python
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Eoan: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
python-pbr_5.1.1.orig.tar.gz 110.8 KiB f59d71442f9ece3dffc17bc36575768e1ee9967756e6b6535f0ee1f0054c3d68
python-pbr_5.1.1-0ubuntu3.debian.tar.xz 9.2 KiB f31161782f2e1926af070cbbe030f733254cb73bec6c77022645fcd57f58aefe
python-pbr_5.1.1-0ubuntu3.dsc 3.2 KiB cb9e98213a6a700bce200488784cdb3b41cb993112b8fe450b49c377bb3bbd18

Available diffs

View changes file

Binary packages built by this source

python-pbr: inject useful and sensible default behaviors into setuptools - Python 2.x

 PBR (Python Build Reasonableness) is a library that injects some useful and
 sensible default behaviors into your setuptools run. PBR can:
  * Manage version number based on git revisions and tags (Version file).
  * Generate AUTHORS file from git log
  * Generate ChangeLog from git log
  * Generate Sphinx autodoc stub files for your whole module
  * Store your dependencies in a pip requirements file
  * Use your README file as a long_description
  * Smartly find packages under your root package
 .
 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.
 .
 This package provides support for Python 2.x.

python-pbr-doc: No summary available for python-pbr-doc in ubuntu eoan.

No description available for python-pbr-doc in ubuntu eoan.

python3-pbr: inject useful and sensible default behaviors into setuptools - Python 3.x

 PBR (Python Build Reasonableness) is a library that injects some useful and
 sensible default behaviors into your setuptools run. PBR can:
  * Manage version number based on git revisions and tags (Version file).
  * Generate AUTHORS file from git log
  * Generate ChangeLog from git log
  * Generate Sphinx autodoc stub files for your whole module
  * Store your dependencies in a pip requirements file
  * Use your README file as a long_description
  * Smartly find packages under your root package
 .
 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.
 .
 This package provides support for Python 3.x.