It looks like we've run out of things to say about PEP 517, except, how soon can we get it into pip? These function signatures will serve us well, significantly lowering the barrier to entry for new pip-compatible build systems. On Thu, Jul 20, 2017 at 3:36 PM Brett Cannon <brett@python.org> wrote:
On Thu, 20 Jul 2017 at 03:56 Nathaniel Smith <njs@pobox.com> wrote:
On 20 July 2017 at 10:46, Nathaniel Smith <njs@pobox.com> wrote:
To make this concrete: I'm *pretty* sure (?) that at this point all the basic elements in my "simplified" rewrite are things that we now have consensus are needed in some form, so maybe we can use that as a kind of "minimal core" reference point:
https://github.com/njsmith/peps/commits/517-refactor-streamline/pep-0517.txt
I don't have time this week to look at this, sorry, but a couple of
On Thu, Jul 20, 2017 at 3:22 AM, Paul Moore <p.f.moore@gmail.com> wrote: points:
1) This links to a commit in your repo, not to the actual document.
Ugh, sorry! Pasted the wrong link. This is the correct one:
https://github.com/njsmith/peps/blob/517-refactor-streamline/pep-0517.txt
Also, I'd *really* prefer a rendered version if I'm going to review this.
Annoyingly, the PEPs repo uses a .txt extension for .rst files, thus cleverly preventing github from doing anything useful by default...
We will happily accept help in converting plaintext PEPs into reST ones so we can universally change the file extensions to .rst (see https://github.com/python/peps/issues/1) :)
-Brett _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig