On Thu, 27 Sep 2018 at 00:11, Paul Ganssle <p...@ganssle.io> wrote: > > Sorry it's taken me a while to respond in this thread, but I think I'd > like to slightly reframe the question away from `setuptools` > specifically - considering that certain requirements are standardized in > the Core Metadata specification, might it make sense to add those to the > core spec for `pyproject.toml`, so that there's a single standard way > for various tools to look for the install dependencies of a project? > > > This would involve adding something like a `distribution.requires` and > possibly `distribution.requires-python`, which would map more or less > directly to `Requires-Dist` and `Requires-Python`.
These dependencies are an *output* of the release artifact build process, so they don't belong in a build process *input* file. (This is in stark contrast build dependencies: you need those in order to build the release artifacts, so it makes sense to put them in the input file. However, even there, PEP 517 offers a mechanism for the build system to request installation of additional dependencies dynamically) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-le...@python.org https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/TJVBJO2NPYJZLR5NNQ5LVVJZFLTGQXRF/
