Design-by-Committee

[Michal Spalinski]

Steve Cooper <stevencooper at isomedia.com> writes:

> When the quantity of double-underscore tags in typical Python scripts starts
> approaching the number of dollar signs in typical Perl scripts that's when I
> jump onto Ruby, or whatever the next great hope will be. :-)

An alternative scenario would be to stick to Python 1.5.2. If the current
rush to change the core language continues then perhaps one day some group
of individuals will take on the task of maintaining the libraries that came
with 1.5.2: i.e. fix bugs that have come to light since 1.5.2 was released
and "port" any new libraries which appear in the "evolving" Python.


> 
> Regards,
> |steve
> 
> Andrew Kuchling wrote:
> 
> > root at 127.0.0.1 (David) writes:
> > > Is the primary focus these days on adding new language
> > > features/commands/components, or on cleaning up the existing codebase?
> >
> > It seems to mostly be on new language features (iterations,
> > generators, unifying types and classes).  I think this effort is
> > mostly misplaced; raw language features are rarely a reason to choose
> > one language over another, the availability of libraries being a more
> > critical issue.  Sadly the development team seems to have forgotten
> > this.
> >
> > --amk
> > --
> > http://mail.python.org/mailman/listinfo/python-list
> 
>