On 23 July 2016 at 21:24, Guido van Rossum wrote:
> I encourage adding this flow to PEP 1 so that it's clear that it's
> supported, and also to ensure that the flow doesn't ignore python-dev.
OK, I'll pull together a PR for PEP 1.
Paul
___
python-commit
On Sat, Jul 23, 2016, 13:17 Brett Cannon wrote:
>
>
> On Sat, Jul 23, 2016, 12:15 Paul Moore wrote:
>
>> With PEPs now being hosted on github, is there any specific process
>> for handling reviews/discussions on the github tracker? PEP 1 doesn't
>> mention the matter, other than to note that dis
I encourage adding this flow to PEP 1 so that it's clear that it's
supported, and also to ensure that the flow doesn't ignore python-dev.
On Sat, Jul 23, 2016 at 1:15 PM, Barry Warsaw wrote:
> On Jul 23, 2016, at 08:15 PM, Paul Moore wrote:
>
>>With PEPs now being hosted on github, is there any s
On Sat, Jul 23, 2016, 12:15 Paul Moore wrote:
> With PEPs now being hosted on github, is there any specific process
> for handling reviews/discussions on the github tracker? PEP 1 doesn't
> mention the matter, other than to note that discussions "may also
> occur on a list other than python-dev"
On Jul 23, 2016, at 08:15 PM, Paul Moore wrote:
>With PEPs now being hosted on github, is there any specific process
>for handling reviews/discussions on the github tracker? PEP 1 doesn't
>mention the matter, other than to note that discussions "may also
>occur on a list other than python-dev" alt
With PEPs now being hosted on github, is there any specific process
for handling reviews/discussions on the github tracker? PEP 1 doesn't
mention the matter, other than to note that discussions "may also
occur on a list other than python-dev" although the approach of having
a Discussions-To header
