nhodgson at bigpond.net.au
Sat Aug 4 02:18:32 CEST 2001
> You have lots of good ideas and suggestions from others. /Please/ don't
> change Python to accommodate them all; it would spoil it. Put them into a
> /new/ language. Maybe even build in call and data level compatibility so
> they can be well integrated. Then people can choose whichever one is best
> for the task.
That is what Guido is doing. The current language is Python 2.1, future
languages will be called Python 2.2, Python 3.0, and so forth. If you really
don't want the language to change in any way, the right thing to do is to
fork the current implementation into a stability branch which can continue
to receive bug fixes, performance improvements and license changes.
This may interest other developers enough to contribute. Then again, it
More information about the Python-list