On 29 July 2017 at 06:58, Thomas Kluyver <tho...@kluyver.me.uk> wrote: > On Fri, Jul 28, 2017, at 09:37 PM, Daniel Holth wrote: > > See how trivial it would be to put the delegated sdist generator into the > build-backend within the confines of the current PEP? > > I agree that delegation within the backend is a reasonable answer to this.
Yeah, I think the way to lower this particular barrier to entry is through a traditional helper module, or in the absence of that, folks just copying ideas and code from existing permissively licensed backends like flit and enscons. As for when this idea came up originally, I'm pretty sure at least *I* suggested it at one point, and was subsequently persuaded to change my mind by the above argument :) So while I don't think we should change the proposal, it may be worth listing "Separate sdist and wheel building backends" explicitly in the "Rejected Options" section, with the rationale that different backends will still be able to share common sdist building code through regular open source development processes. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
