On Tue, 4 Dec 2012 16:45:54 -0500
Brett Cannon <brett@python.org> wrote:
> >
> > +1 for getting this into 3.4. Does it need a PEP, or just a bug
> > tracker item + code review? I think the latter is fine -- it's
> > probably better not to do too much bikeshedding but just to let Larry
> > propose a patch, have it reviewed and submitted, and then iterate.
> > It's also okay if it is initially used for only a subset of extension
> > modules (and even if some functions/methods can't be expressed using
> > it yet).
> >
>
> I don't see a need for a PEP either; code review should be plenty since
> this doesn't change how the outside world views public APIs. And we can
> convert code iteratively so that shouldn't hold things up either.

I think the DSL itself does warrant public exposure. It will be an
element of the CPython coding style, if its use becomes widespread.

That's what the issue will tease out, so this isn't going in without some public scrutiny. But going through python-ideas for this I think is a bit much. I mean we don't clear every change to PEP 7 or 8 with the public and that directly affects people as well in terms of coding style.
">

(original) (raw)




On Tue, Dec 4, 2012 at 4:48 PM, Antoine Pitrou <solipsis@pitrou.net> wrote:

On Tue, 4 Dec 2012 16:45:54 -0500
Brett Cannon <brett@python.org> wrote:
\> >
\> > +1 for getting this into 3.4\. Does it need a PEP, or just a bug
\> > tracker item + code review? I think the latter is fine -- it's
\> > probably better not to do too much bikeshedding but just to let Larry
\> > propose a patch, have it reviewed and submitted, and then iterate.
\> > It's also okay if it is initially used for only a subset of extension
\> > modules (and even if some functions/methods can't be expressed using
\> > it yet).
\> >
\>
\> I don't see a need for a PEP either; code review should be plenty since
\> this doesn't change how the outside world views public APIs. And we can
\> convert code iteratively so that shouldn't hold things up either.

I think the DSL itself does warrant public exposure. It will be an
element of the CPython coding style, if its use becomes widespread.

That's what the issue will tease out, so this isn't going in without some public scrutiny. But going through python-ideas for this I think is a bit much. I mean we don't clear every change to PEP 7 or 8 with the public and that directly affects people as well in terms of coding style.