[Distutils] build system requirements PEP, 3rd draft (original) (raw)

Nick Coghlan ncoghlan at gmail.com
Mon May 16 03:02:03 EDT 2016

On 14 May 2016 at 05:03, Brett Cannon <brett at python.org> wrote:

Biggest changes since the initial draft:

1. No more semantics-version 2. No more [package] table 3. Settled on [build-system] as the table name 4. The "requires" key is required if [build-system] is defined 5. Changed the title and clarified that this is all about the minimum requirements for the build system to execute (some added support for things like dynamic dependencies for producing build artifacts is for another PEP)

And lo, the colour of the bikeshed was chosen, and the chosen colour was "teal" :)

More seriously, as BDFL-Delegate, I'm entirely happy with this version. Thanks for your work in pulling this reduced scope PEP together, as well as to Robert, Nathaniel and Donald in driving the preceding build system invocation PEPs.

While it's a deviation from the nominal PEP process, I figure you can check this into the PEPs repo in an already Accepted state, with a reference back to this email for the Resolution. Once the PEPs repo itself allows for pull requests, I except we'll adjust the numeric identifier allocation process to include checking for open PRs and using the next number not used in a current PR, rather than the next number not used in the repo itself.

Added a JSON Schema for the resulting data from the table because Nick likes his specs :)

Working for Boeing for so long left its mark :)

Cheers, Nick.

-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia

More information about the Distutils-SIG mailing list