Python 1.5.x vs Python 2.x.x
Suchandra Thapa
ssthapa at classes.cs.uchicago.edu
Thu Dec 20 17:20:46 EST 2001
Andrew Kuchling <akuchlin at mems-exchange.org> wrote:
>Paul Rubin <phr-n2001d at nightsong.com> writes:
>> That's a good point. It's probably too late to start reporting the
>> incompatibilities as bugs against 2.2c, though that's what they are.
>
>And if no one reports bugs, they can't get fixed. You could still go
>ahead and report them, but unless they're real showstoppers they won't
>be fixed in 2.2final, which is being wrapped up even as we speak. I
>don't know if it'll be considered worth fixing them in 2.3.
>
>(Or is this talk of incompatibilities simply FUD from people who are
>scared of upgrading?)
I think Paul was referring more to changes in modules or syntax that
broke previous scripts. For example, the rand module had a name change
to random. Scripts that used the rand module will break with an
ImportError if they are run under 2.x. I believe there were a few other
things like this where things were intentionally changed but prevented
backwords compatibility. Not bugs per se unless perfect backward
compatibility was an overriding concern.
--
----------------------------------------------------------------------------
|
Suchandra Thapa | "There are only two kinds of math .
s-thapa-11 at NOSPAMalumni.uchicago.edu | books. Those you cannot read beyond
| the first sentence, and those you
| can not read beyond the first page."
| -C.N. Yang
----------------------------------------------------------------------------
More information about the Python-list
mailing list