From: clift at mail.anacapa.net (Steve Clift)
Date: Wed, 26 May 1999 19:34:16 -0700
Subject: Python 1.5.2 and large files (Solaris 7)
In-Reply-To: <000301bea731$df6496a0$529e2299@tim>
References: <3.0.6.32.19990525184325.0094e100@mail.anacapa.net>
Message-ID: <3.0.6.32.19990526193416.00960c10@mail.anacapa.net>
X-UID: 1736                                                

At 12:40 AM 1999-05-26 -0400, the night watchman wrote:

>[about whether integer-yielding ops on huge files should always return long,
> or cut back to int when they're small enough]

[snip]

>When I get back a position from f.tell() and add 1017 to it, knowing a
>priori that the sum is also a valid position for the file, I don't ever want
>to see an OverflowError.  I hope Python2 obliterates the user-visibile
>distinction between ints and longs, but in Python1 int arithmetic can
>overflow, and file positions (whether computed or revealed) are expected to
>overflow an int in the presence of huge files.
>
>all-long-all-the-time-so-long-as-it-matters-ly y'rs  - tim

Checkmate. Now I feel strongly about it.

How do you come up with this sort of stuff at such an hour?

-Steve






