On Sat, Nov 18, 2017 at 5:28 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > > Ah, OK - this makes sense. > > Framing it in terms of the required input file, the two most suitable > names would be: > > * "pyproject.toml compatible spec files" > * "setup.py only spec files" > > I'd suggest keeping the current wheel-centric macro names, though, and > just adjust the wheel building macro to accept pyproject.toml files in > addition to setup.py files. > +1, Sound good
> In that case, I'd lean towards emphasising the macros in the > guidelines, and then pointing towards the macro definitions in > dist-git if folks really want to dig into the details of what the > macros actually do. However, we'd also keep the various sections that > explain how to do various lower level things correctly (like > precompiling Python files), since those providing the "Why?" of > various decisions, which simply reading the macro source files won't > give you. > <nod>m his makes sense to me too. Thanks Nick! -Toshio _______________________________________________ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
