Python 2.0 naive question

[Aahz Maruch]

In article <8qfrva$75$1 at nnrp1.deja.com>,  <drobinow at my-deja.com> wrote:
>
>  You say, "I'm not going to move to 2.0 until it's stable
>   because this project is too important and I'm afraid there'll
>   be some incompatibility that will make my code fail."
>  Python 2.0final is released and everybody in the world loves it.
>  There turns out to be an obscure incompatibility with 1.5.2 that
>   could have been easily fixed if anybody had noticed. It prevents
>   you from going to 2.0.
>  Nobody wants to use your product because it is based on obsolete
>   technology.

Hogwash.  Many people didn't move to 1.5.2 for nearly a year after it
was released; I expect an even longer cycle time for 2.0 with all of its
changes.  A year is more than enough time to address those issues.
-- 
                      --- Aahz (Copyright 2000 by aahz at pobox.com)

Androgynous poly kinky vanilla queer het    <*>     http://www.rahul.net/aahz/
Hugs and backrubs -- I break Rule 6

Member of the Groucho Marx Fan Club  --Aahz