On Wed, 11 May 2016 17:11:54 +1000 Nick Coghlan <ncogh...@gmail.com> wrote: > > Take the default case: for a distutils/setuptools based project, the > actual build settings are the arguments to setup() in setup.py, *not* > these new settings in pyproject.toml. By contrast, the settings in > [package.build-system] are the ones that tell pip and other installers > what is needed to make "setup.py bdist_wheel" work (and, in the > future, will tell them when to invoke something other than "setup.py > bdist_wheel" to do the binary build)
Side question: if the build system needs configuring, is a user-provided configuration file really the best place to do so? People will end up having to copy and paste a bunch of configuration directives that are not directly relevant to their own project (also those directives will need maintaining as a build tool may evolve its dependencies over time). Alternative: have a single "build system" configuration directive: [package.build-system] tool = "foopackage:fooexe" ... which instructs the runner to install dependency "foopackage", and then invoking "fooexe" with a single well-known option (e.g. "--pybuild-bootstrap-config") produces a JSON file on stdout describing how to invoke precisely the tool for each build scenario (sdist, wheel, etc.). Regards Antoine. _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
