Larry Hastings <larry@hastings.org> wrote:
> � � http://bugs.python.org/issue16612
>
> I'm guessing python-dev is the right place for the ten-thousand-foot view
> topics: the merits of the specific proposed DSL syntax, the possible runtime
> extension API, and the approach as a whole. �So for now let's just use the bug
> tracker issue for code reviews and the like.

For anyone who isn't following the issue: A PEP proposing a different DSL
will be forthcoming either this or next weekend.

If the two proposals share at least the motivation, would it not be more constructive to just have them listed as alternatives in a single PEP? This could serve as a useful single source of information for the new proposed features.
">

(original) (raw)

On Tue, Feb 26, 2013 at 12:30 AM, Stefan Krah <stefan@bytereef.org> wrote:
Larry Hastings <larry@hastings.org> wrote:
\> � � http://bugs.python.org/issue16612
\>
\> I'm guessing python-dev is the right place for the ten-thousand-foot view
\> topics: the merits of the specific proposed DSL syntax, the possible runtime
\> extension API, and the approach as a whole. �So for now let's just use the bug
\> tracker issue for code reviews and the like.

For anyone who isn't following the issue: A PEP proposing a different DSL
will be forthcoming either this or next weekend.

If the two proposals share at least the motivation, would it not be more constructive to just have them listed as alternatives in a single PEP? This could serve as a useful single source of information for the new proposed features.


Eli