[Python-Dev] On the necessity of PEPs [was "collections.sortedtree"]
Antoine Pitrou
solipsis at pitrou.net
Fri Mar 28 12:12:07 CET 2014
More information about the Python-Dev mailing list
Fri Mar 28 12:12:07 CET 2014
- Previous message: [Python-Dev] On the necessity of PEPs [was "collections.sortedtree"]
- Next message: [Python-Dev] On the necessity of PEPs [was "collections.sortedtree"]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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. Regards Antoine.
- Previous message: [Python-Dev] On the necessity of PEPs [was "collections.sortedtree"]
- Next message: [Python-Dev] On the necessity of PEPs [was "collections.sortedtree"]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list