RetroSearch Browse

Fri Mar 28 12:18:58 CET 2014 · https://mail.python.org/pipermail/python-dev/2014-March/133649.html

On 28 March 2014 21:12, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Thu, 27 Mar 2014 20:32:02 +1000
> Nick Coghlan <ncoghlan at gmail.com> wrote:
>>
>> Most of the time when I hear people say "the PEP process is too
>> difficult", I eventually find that what they really mean is "learning
>> the kinds of things that python-dev are likely to be worried about,
>> and ensuring that the PEP adequately addresses their concerns, and
>> listening to feedback, and reconsidering what I actually want, and
>> revising my proposal, such that they eventually say yes is too time
>> consuming".
>
> Well, the PEP process *is* difficult and not only because you have to
> learn the kinds of things that python-dev are likely to be worried
> about. Getting a PEP accepted for a feature is much more work than
> getting a feature accepted in the bug tracker.

Oh, agreed. It's only the "too" qualifier that I question - I'm not
sure how much easier we could make it before it ceased to serve its
filtering purpose.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-March/133649.html below:

[Python-Dev] On the necessity of PEPs [was "collections.sortedtree"]