On 27 Jul., 13:21, Dave Angel wrote:
> (forwarding this message, as the reply was off-list)
>
>
>
> Kim Hansen wrote:
> > 2009/7/24 Dave Angel :
>
> >> It's not a question of how much disk space there is, but how much virtual
> >> space 32 bits can address. 2**32 is about 4 gig, and Windows XP re
(forwarding this message, as the reply was off-list)
Kim Hansen wrote:
2009/7/24 Dave Angel :
It's not a question of how much disk space there is, but how much virtual
space 32 bits can address. 2**32 is about 4 gig, and Windows XP reserves
about half of that for system use. Presumably a 64
Slaunger wrote:
OS: Win XP SP3, 32 bit
Python 2.5.4
Hi I have run into some problems with allocating numpy.memmaps
exceeding and accumulated size of about 2 GB. I have found out that
the real problem relates to numpy.memmap using mmap.mmap
I've written a small test program to illustrate it:
im
> Slaunger (S) wrote:
>S> OS: Win XP SP3, 32 bit
>S> Python 2.5.4
>S> Hi I have run into some problems with allocating numpy.memmaps
>S> exceeding and accumulated size of about 2 GB. I have found out that
>S> the real problem relates to numpy.memmap using mmap.mmap
On Windows XP the virtual
Slaunger schrieb:
OS: Win XP SP3, 32 bit
Python 2.5.4
Hi I have run into some problems with allocating numpy.memmaps
exceeding and accumulated size of about 2 GB. I have found out that
the real problem relates to numpy.memmap using mmap.mmap
I've written a small test program to illustrate it:
OS: Win XP SP3, 32 bit
Python 2.5.4
Hi I have run into some problems with allocating numpy.memmaps
exceeding and accumulated size of about 2 GB. I have found out that
the real problem relates to numpy.memmap using mmap.mmap
I've written a small test program to illustrate it:
import itertools
imp
