will python 3000 break my code?

[Charles Cazabon]

Michal Wallace claimed in <87tkoi$hql$1 at nntp1.atl.mindspring.net>:

>   I noticed this just recently on http://www.python.org/1.5/ ...
>
>> The new release schedule provides for a 1.7
>> release later in 2000 (or early 2001); after that,
>> we'll be working on "Python 3000" (the new code
>> name for the grand Python redesign; the language
>> will be incompatible).

>"The language will be incompatible"  seems like kind
>of a dangerous statement to be making without
>backing it up... As much as I love python, for example,
>I can't very well recommend using it if everything I
>write will have to be thrown out in a year or two.

Who says you have to throw anything out?  Your trusty Python v.1.5.2 (or 
1.6, or 1.7) doesn't magically stop working the day 'Python 3000' is 
released.

Rule of Software Systems:  Upgrade software when it fixes bugs you need 
fixed, or adds features you need added.  Never anytime else.

Charles