On 1/12/07, Mike Orr <[EMAIL PROTECTED]> wrote:

On 1/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> The benefit (to me, and to many others) of 3.x over 2.x is the promise
of
> more future maintenance, not the lack of cruft.

The benefit (to me, and to many others) of 3.x over 2.x is the promise
of getting rid of cruft.

If we're going to re-add cruft for the sake of temporary
compatibility, we may as well just stick with 2.x.  You have to take a
quantum leap sometimes or you end up working around the same old
mistakes.


There seems to be rather a lot of confusion. No one is suggesting
Python 3.0be anything less for the sake of backward compatibility.
Instead, it has
been suggested Python 2.6 (and possibly 2.7) be something *more* in order to
provide for an easier upgrade path. No compromises in Python 3.0.

--
Thomas Wouters <[EMAIL PROTECTED]>

Hi! I'm a .signature virus! copy me into your .signature file to help me
spread!
_______________________________________________
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

Reply via email to