Thanks for the suggested bikeshed topic. Clever! I like build also. "package build requires". I see that build is what you used in the example [rejected] file formats. To me further segmentation between build systems and the actual build that the build system effects is something you might do to avoid the cost of installing a dependency that might not actually be needed during that phase. IMO installation of an occasional extra package is a fair price to pay if it reduces the number of concepts in the system.
On Wed, May 11, 2016 at 10:26 AM Antoine Pitrou <solip...@pitrou.net> wrote: > On Thu, 12 May 2016 00:20:32 +1000 > Nick Coghlan <ncogh...@gmail.com> wrote: > > > > When I say "build system configuration" in the context of > > distutils/setuptools, I mean things like: > > > > * MANIFEST.in > > * non-dependency related setup() arguments (packages, package_dir, > > py_modules, ext_modules, namespace_packages, entry_points, > > include_package_data, zip_safe, etc) > > * the Extension class and its parameters: > > > https://docs.python.org/2/distutils/setupscript.html#describing-extension-modules > > > > Those are the settings that actually tell the build system what to > > build and (in some cases) how to build it. > > That's confusing :-) You should really call it "build configuration". > > Regards > > Antoine. > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
