Message from discussion Python Gotcha's?
Received: by 10.68.125.233 with SMTP id mt9mr8769960pbb.5.1334559095374;
Sun, 15 Apr 2012 23:51:35 -0700 (PDT)
From: Bryan <bryanjugglercryptograp...@yahoo.com>
Subject: Re: Python Gotcha's?
Date: Sun, 15 Apr 2012 23:44:13 -0700 (PDT)
X-Trace: posting.google.com 1334559095 10857 127.0.0.1 (16 Apr 2012 06:51:35 GMT)
NNTP-Posting-Date: Mon, 16 Apr 2012 06:51:35 +0000 (UTC)
Injection-Info: n5g2000pbg.googlegroups.com; posting-host=126.96.36.199; posting-account=J5j24gkAAABQ9Yx9iE8ZAnhHMzpxizi7
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0,gzip(gfe)
Content-Type: text/plain; charset=windows-1252
Steven D'Aprano wrote:
> And how is that different from any other two versions of Python?
Python 3.0, also known as =93Python 3000=94 or =93Py3K=94, is the first eve=
*intentionally backwards incompatible* Python release. --GVR
> Unless both versions include the same libraries (either standard modules
> or third party), and your code is written to use only the lowest common
> denominator functionality, you will have problems regardless of which
> versions they are.
*My* code is not what's holding me back. I *like* moving my code to
Python 3. What's holding me back is library availability, and from
various readings on the transition to 3, I gather that's what holding
many, perhaps most, users back.
The need to keep using 2.x should not stop users from installing and
starting to muck with 3.0. That's much more painful than it has to be
because they both use the same file extension.