On 2 June 2017 at 08:49, Nick Coghlan <ncogh...@gmail.com> wrote: > The last point means that requiring an sdist export command shouldn't > impose an unreasonable burden on backend developers, as the only > differences between "generate an sdist tree" and "export a build tree" > would be: > > - `pyproject.toml` MUST be included unmodified at the root of the sdist tree > - `PKG-INFO` MUST be generated at the root of the sdist tree > - a `setup.py` shim MAY be generated for backwards compatibility with > installation tools that are unaware of PEP 517
Note that a full "build an sdist" process should include a means for authors to add extra files (such as README, LICENSE, ...). But that can be either something that backends deal with themselves or (better) gets standardised in a separate PEP (probably defining a new set of `pyproject.toml` fields for it). It's not inherently something we need right now in PEP 517. Paul _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
