Build Changes

[dmtucker]

pypa/pip#6041 (2018-11-25) leads to https://discuss.python.org/t/building-distributions/2062 where the latest post (2020-06-15) reads:

Moving python-build to PyPA is a discussion about taking the route of going down option 3 (see original post for what this thread was for).

python-build has an illuminating section in its documentation, particularly regarding pep517.build:

pep517.build contained a proof-of-concept of a PEP 517 frontend. It “implement[ed] essentially the simplest possible frontend tool, to exercise and illustrate how the core functionality can be used”. It has since been deprecated and is scheduled for removal.

The linked PR regarding deprecation/removal has since been merged (2020-09-03), but, interestingly, it may be reverted by pypa/pyproject-hooks#96 as part of Moving users away using pep517 as a CLI tool (2020-09-08).

Anyways, apparently a vote regarding the migration of python-build to PyPA was to be proposed in the last week according to https://github.com/FFY00/python-build/issues/42. Needless to say, pep517.build should probably be ditched for python-build:

backlog/tox.ini

Lines 58 to 67 in e70f015

	[testenv:publish]
	basepython = python3.8
	ignore_basepython_conflict = true
	passenv = TWINE_*
	deps =
	pep517 ~= 0.8.0
	twine ~= 3.2.0
	commands =
	{envpython} -m pep517.build --out-dir {distdir} .
	twine {posargs:check} {distdir}/*