summaryrefslogtreecommitdiff
path: root/releasenotes/notes/pep517-support-89189ce0bab15845.yaml
diff options
context:
space:
mode:
authorMonty Taylor <mordred@inaugust.com>2021-06-24 08:24:30 -0400
committerClark Boylan <clark.boylan@gmail.com>2021-11-03 10:05:32 -0700
commit09ee15341014fc0e3bb8a7c3b06a3fa912cfad38 (patch)
tree565f7ec56e003422a25701d757b2a412b07dd07a /releasenotes/notes/pep517-support-89189ce0bab15845.yaml
parent8c0d5c314108c09bbb3004d608a5a95bd81b8820 (diff)
downloadpbr-5.7.0.tar.gz
Add a PEP517 interface5.7.0
pep517 defines a new module method of specifying build backends. To allow pbr to exist in this world, we should define the interface that's needed. For this to be used, one will put: [build-system] requires = ["pbr>=5.7.0", "setuptools>=36.6.0", "wheel"] build-backend = "pbr.build" Into pyproject.toml - and the pep517 interface will be used. This doesn't really change anything else - it just makes us support this. So by itself this commit isn't SUPER helpful. But maybe let's take baby steps with something this prone to strife, yeah? After this we can start teasing some things apart and doing our own things directly. Co-Authored-By: Clark Boylan <clark.boylan@gmail.com> Change-Id: I293f59b5074a38c78adffe580de2f1533bb01ce7
Diffstat (limited to 'releasenotes/notes/pep517-support-89189ce0bab15845.yaml')
-rw-r--r--releasenotes/notes/pep517-support-89189ce0bab15845.yaml7
1 files changed, 7 insertions, 0 deletions
diff --git a/releasenotes/notes/pep517-support-89189ce0bab15845.yaml b/releasenotes/notes/pep517-support-89189ce0bab15845.yaml
new file mode 100644
index 0000000..97ab28b
--- /dev/null
+++ b/releasenotes/notes/pep517-support-89189ce0bab15845.yaml
@@ -0,0 +1,7 @@
+---
+features:
+ - |
+ PBR now includes a PEP 517 build-backend and can be used in
+ pyproject.toml build-system configuration. Setuptools continues
+ to be the underlying mechanism with PBR acting as a driver via
+ PEP 517 entrypoints.