[Python-Dev] Re: Feature bloat in Python (was some PEP thing!)

[Fredrik Lundh]

mark wrote:

> If you can't quickly and quietly win this friendly audience over, IMO =
the
> proposal has failed.  If any proposal causes even a small thread on =
this
> forum that boils down to "but its not clear to me what this should =
do",
> then I would have thought it self-evident that the proposal sucks.
> Convincing us that it _should_ be obvious if only we were all a little
> brighter and more willing to accept change for changes sake doesn't
> help anyone, least of all the person making these statements

from the new Tcl Code Team rules:

    "A project can also be proposed by someone outside the Tcl Core
    Team, but it can't be approved without an advocate on the Tcl
    Core Team who will take personal responsibility for it. A project
    must have support from at least 2 members of the Tcl Core Team
    (including the proposer); if anyone in the Tcl Core Team objects
    to the proposal, then there must be at least 4 members in favor
    (including the proposer). If there are two or more "no" votes then
    the proposal is rejected, regardless of the number of people in
    favor.

    "The idea here is that the Tcl Core Team can only work effectively
    if it is highly collegial; any project that generates significant =
contro-
    versy should not go into the Tcl core."

and for the record, I'm fully prepared to vote "no" on list =
comprehensions,
augumented assignments, range literals, and every trace of a new =
operator
that changes how python code is tokenized and parsed.

not that it will change anything:

> Thanking-God-Python-isnt-being-designed-by-this-committee-ly

...with two major releases with only a few weeks in between, I'm afraid =
we'll
see the usual "do we really need this?" rule being replaced with "what =
can we
add to make sure people know there's really a difference?".  obviously, =
things
with fancy names and existing patches are on the top of that list :-(

</F>