Debugging Python 1.3 -> 1.5.2 (was Re: Python 1.6 alpha 1 released)

[Aahz Maruch]

In article <FdoG4.5023$74.81126 at newsc.telia.net>,
Fredrik Lundh <effbot at telia.com> wrote:
>
>   [....]
>I suggest you dig up my list of "change cost" criterias, and apply
>them to all non-compatible changes (possibly starting with 1.5.2's
>class object change, which broke *lots* of code in really naughty
>ways [1]).  I've done that, and I still think that "connect" is the
>*least* critical of all code-breaking changes in the python core,
>since 1.3 or so.
>
>   [....]
>1) stumbled upon one today: it turned out that by changing from 1.3
>to 1.5.2, large data transfers from a high-performance server to clients
>on an 10 Mbit Ethernet were unexpectedly terminated.  the same trans-
>fers worked just fine with high-performance workstations, on an FDDI
>network.  ten guru points to anyone who can explain why.

Not without a bit more info about the data transfer mechanism and the
error reported by client & server.
--
                      --- Aahz (Copyright 2000 by aahz at netcom.com)

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

"It's 106 miles to Chicago.  We have a full tank of gas, a half-pack of
cigarettes, it's dark, and we're wearing sunglasses."  "Hit it."