Thoughts about extensions to the Python language

Jeremy Hylton jeremy at alum.mit.edu
Wed Mar 14 17:37:18 EST 2001


Guido did a poll at developers day last week.  The question was: "Is
Python development moving too fast or at just the right speed?"  (He
was being dictatorial and didn't even consider votes from the
more-faster crowd.)

I believe the results were 42 too fast and 50 just right.  I noted
that two of the more vocal proponents of the too fast camp proceeded
to suggest new features.  So at least some of the "too fast" people
probably meant "too fast unless it's a feature I want" :-).

Several people also suggested that Python 2.0 was a fine release, but
there were too many new things in Python 2.1.  Other than nested
scopes, which aren't slated for standard arrival until 2.2, there
aren't very many new features in 2.1 -- rich comparisons, a warnings
framework, support for weak references.  Rich comparisons, to pick an
example, have been on the table for ages.  The numeric people seem
happy, because NumPy has already added support for them.

You seem to have a very abstract concern about the speed of
develpoment and the fact that we write design documents that describe
changes to the language.  I voted for "just right" in the poll, so we
probably don't agree on the former.  As for the latter, what
alternative is there?  Make changes to the language without
describing the changes in advance? <wink>  I don't expect Guido's good
judgement is impaired by having written proposals to consider.  He's
been known to reject PEPs.

Jeremy




More information about the Python-list mailing list