On Sat, 22 May 2010 10:09:37 -0400, Jesse Noller <jnol...@gmail.com> wrote: > On Sat, May 22, 2010 at 9:59 AM, R. David Murray <rdmur...@bitdance.com> wr= > ote: > > On Sat, 22 May 2010 19:12:05 +1000, Brian Quinlan <br...@sweetapp.com> wr= > ote: > >> On May 22, 2010, at 5:30 AM, Dj Gilcrease wrote: > >> > On Fri, May 21, 2010 at 8:26 AM, Brian Quinlan <br...@sweetapp.com> > >> > wrote: > >> >> Except that now isn't the time for that discussion. This PEP has > >> >> discussed > >> >> on-and-off for several months on both stdlib-sig and python-dev. > >> > > >> > I think any time till the PEP is accepted is a good time to discuss > >> > changes to the API > >> > >> I disagree. If a PEP is being updated continuously then there is > >> nothing stable to pronounce on. > > > > Well, you've been making updates as a result of this round of > > discussion. > > > > If there is still discussion then perhaps the PEP isn't ready for > > pronouncement yet. =A0At some point someone can decide it is all > > bikeshedding and ask for pronouncement on that basis, but I don't > > think it is appropriate to cut off discussion by saying "it's ready for > > pronouncement" unless you want increase the chances of its getting > > rejected. > > I commiserate with Brian here - he's been very patient, and has been > working on things, taking in input, etc for awhile now on this. In his > mind, it is done (or at least incredibly close to done) and opening > the door in the conversation for more API nit picking and debate about > the exact verbiage on method names means we're never going to be done > splashing paint.
OK, so you are saying that the comments in question are bikeshedding. I can accept that easily. What I was trying to point out was that saying "discussion is closed" is not the best way to nurture community consensus. Saying "we've reached the bikesheedding point, let's pronounce" is a very different thing to my mind, even if it is only a matter of tone. Have fun pronouncing ;) -- R. David Murray www.bitdance.com _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
