We should take the discussion about how and where PEP discussions should be
hosted off this thread and list.
On Wed, May 23, 2018 at 6:59 AM, Nick Coghlan wrote:
> On 23 May 2018 at 05:47, Guido van Rossum wrote:
>
>> On Tue, May 22, 2018 at 10:07 AM, Steve Dower
>> wrote:
>>
>>> On 22May2018
On 23 May 2018 at 05:47, Guido van Rossum wrote:
> On Tue, May 22, 2018 at 10:07 AM, Steve Dower
> wrote:
>
>> On 22May2018 0741, Guido van Rossum wrote:
>>
>>> ISTR there are plenty of PEPs that never get posted to python-ideas
>>> because they are discussed on a separate list.
>>>
>>
>> There
For the record: the only reason that I replied on GitHub was because the
proposal was not yet posted (as far as I know) to any mailing list.
Typically, a post is made to a mailing list more or less at the same
time as creating the PEP. In this case, there was a delay of a few days,
maybe also
On Tue, May 22, 2018 at 10:07 AM, Steve Dower
wrote:
> On 22May2018 0741, Guido van Rossum wrote:
>
>> ISTR there are plenty of PEPs that never get posted to python-ideas
>> because they are discussed on a separate list.
>>
>
> There are often better venues for the initial discussion (such as
> s
On 22May2018 0741, Guido van Rossum wrote:
ISTR there are
plenty of PEPs that never get posted to python-ideas because they are
discussed on a separate list.
There are often better venues for the initial discussion (such as
security-sig, distutils-sig or datetime-sig), but I think that's
ort
On Tue, May 22, 2018 at 5:29 AM, Victor Stinner wrote:
> 2018-05-19 11:15 GMT+02:00 mark :
> > The PEP can be viewed here:
> > https://github.com/python/peps/blob/master/pep-0576.rst
> > (...)
> > P.S.
> > I'm happy to have discussion of this PEP take place via GitHub,
> > rather than the mailing
2018-05-19 11:15 GMT+02:00 mark :
> The PEP can be viewed here:
> https://github.com/python/peps/blob/master/pep-0576.rst
> (...)
> P.S.
> I'm happy to have discussion of this PEP take place via GitHub,
> rather than the mailing list, but I thought I would follow the conventional
> route for now.
On 2018-05-19 11:15, mark wrote:
PEP 576 aims to fulfill the same goals as PEP 575
(this is a copy of my comments on GitHub before this PEP was official)
**Performance**
Most importantly, changing bound methods of extension types from
builtin_function_or_method to bound_method will yield a p
mark schrieb am 19.05.2018 um 11:15:
> At the language summit this year, there was some discussion of PEP 575.
> I wanted to simplify the PEP, but rather than modify that PEP, Nick Coghlan
> encouraged me to write an alternative PEP instead.
>
> PEP 576 aims to fulfill the same goals as PEP 575, b
