From: aahz at netcom.com (Aahz Maruch)
Date: Sat, 10 Apr 1999 22:49:09 GMT
Subject: Python 2.0 compatibility
References: <GIOP2.37825$A6.19136587@news1.teleport.com>
Message-ID: <aahzF9zwpx.AnH@netcom.com>
Content-Length: 1379
X-UID: 370                                                  

In article <GIOP2.37825$A6.19136587 at news1.teleport.com>,
Paranoid User <root at localhost> wrote:
>
>We have selected Python as the scripting language for the next generation of
>one of our embedded systems.  This is a very fast-track project scheduled to
>ship near the end of the first quarter of 2000.
>
>I ran across a quote that said something to the effect that Python 2 will be
>incompatible with Python 1.  Before I make a decision as to whether we
>freeze with Python 1.5.2, or migrate to Python 2 when it is released, I need
>to find out the extent of truthfulness in the "quote".

I'm not in the know about Python 2, but I do know this much: Python 2
will almost certainly not ship before your product.  Python 2 has also
not been completely designed yet, so nobody (not even Guido) knows the
extent to which Python 2 will be incompatible.

There's also the likely release of Python 1.6; I don't know whether
that's in parallel with the Python 2 development.

I suggest that you work with 1.5.2 and worry about future releases when
there's more clarity.
-- 
                      --- Aahz (@netcom.com)

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

If they can get you asking the wrong questions, they don't have to worry
about the answers. -- Thomas Pynchon (from EFF quote collection)




