On 6/18/2007 9:24 PM, Mike Ressler wrote:
> What versions of python and numpy are you using?
I am using Python 2.5.1 and Numpy 1.0.3 on Windows XP (32 bit). I
examined the code in SVN, and drew my conclusions from that.
Sidenote on trapping i/o error on Windows:
On Windows, i/o errors must be
On 6/18/2007 9:24 PM, Mike Ressler wrote:
> With python 2.5.1 and numpy 1.0.3 under Fedora 7 x86_64, I just now
> memmap'ed a 10 GB image cube without any trouble.
You have a 64 bit system. On Linux, the off_t uses by mmap's offset is
similar to a size_t. Although the larger off_t on a 64 bit
What versions of python and numpy are you using?
On 6/18/07, Sturla Molden <[EMAIL PROTECTED]> wrote:
> Problem 3: No 64 bit support on Windows or Linux:
>
> On Linux, large files must be memory mapped using mmap64 (or mmap2 if 4k
> boundaries are acceptable). On Windows, CreateFileMapping/MapView
After struggling with NumPy's memmap object, I examined the code and
detected three severe problems. I suggest that memmap is removed from
NumPy, at least on Windows, as it's shortcomings is severe and
undocumented.
Problem 1: I/O errors are never detected on Win32:
On Windows, i/o errors ar
