On 16/08/07, Glen W. Mabey <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 15, 2007 at 08:50:28PM -0400, Anne Archibald wrote:
> > But to be pythonic, or numpythonic, when the original A is
> > garbage-collected, the garbage collection should certainly close the
> > mmap.
>
> Humm, this would be less than
On Wed, Aug 15, 2007 at 08:50:28PM -0400, Anne Archibald wrote:
> You have to be a bit careful, because a view really is just a view
> into the array - the original is still around. So you can't really
> delete the array contents when the view is deleted. Really, if you do:
> B = A[::2]
> del B
> n
On 15/08/07, Glen W. Mabey <[EMAIL PROTECTED]> wrote:
> On Tue, Aug 14, 2007 at 12:23:26AM -0400, Anne Archibald wrote:
> > On 13/08/07, Glen W. Mabey <[EMAIL PROTECTED]> wrote:
> >
> > > As I have tried to think through what should be the appropriate
> > > behavior for the returned value of __geti
Hi,
Thanks for looking into this because we (neuroimaging.scipy.org) use
mmaps a lot. I am very away from my desk at the moment but please do
keep us all informed, and we'll try and pitch in if we can...
Matthew
On 8/15/07, Glen W. Mabey <[EMAIL PROTECTED]> wrote:
> On Tue, Aug 14, 2007 at 12:2
On Tue, Aug 14, 2007 at 12:23:26AM -0400, Anne Archibald wrote:
> On 13/08/07, Glen W. Mabey <[EMAIL PROTECTED]> wrote:
>
> > As I have tried to think through what should be the appropriate
> > behavior for the returned value of __getitem__, I have not been able to
> > see an appropriate solution
On 13/08/07, Glen W. Mabey <[EMAIL PROTECTED]> wrote:
> As I have tried to think through what should be the appropriate
> behavior for the returned value of __getitem__, I have not been able to
> see an appropriate solution (let alone know how to implement it) to this
> issue.
Is the problem one
On Mon, Aug 13, 2007 at 11:51:49AM -0400, Alan G Isaac wrote:
> You have not heard from anyone on this yet, right?
Nope, but I'm glad to hear even this response.
> Please continue to post your findings.
At this point, I'm guessing that the __getitem__() method of ndarray
returns a numpy.memmap i
On Fri, 10 Aug 2007, "Glen W. Mabey" apparently wrote:
> It seems that any slice of a numpy.memmap that is greater than 1-d has
> a similar problem.
> In [1]:import numpy
> In [2]:amemmap = numpy.memmap( '/tmp/afile', dtype=numpy.float32,
> shape=(4,5), mode='w+' )
> In [3]:amemmap[1,3:4]
>
[I keep posting hoping that someone knowledgeable in these things will
take notice ...]
Just a couple of more notes regarding this numpy.memmap issue.
It seems that any slice of a numpy.memmap that is greater than 1-d has
a similar problem.
In [1]:import numpy
In [2]:amemmap = numpy.memmap(
On Fri, Aug 10, 2007 at 11:20:16AM -0500, Glen W. Mabey wrote:
> I posted this a while back and didn't get any replies. I'm running in
> to this issue again from a different aspect, and today I've been trying
> to figure out which method of ndarray needs to be overloaded for memmap
> so that the t
Hello,
I posted this a while back and didn't get any replies. I'm running in
to this issue again from a different aspect, and today I've been trying
to figure out which method of ndarray needs to be overloaded for memmap
so that the the ._mmap attribute gets handled appropriately.
But, I have no
Hello,
When assigning a variable that is the transpose() of a memmap array, the
._mmap member doesn't get copied, I guess:
In [1]:import numpy
In [2]:amemmap = numpy.memmap( '/tmp/afile', dtype=numpy.float32, shape=(4,5),
mode='w+' )
In [3]:bmemmap = amemmap.transpose()
In [4]:bmemmap.close()
12 matches
Mail list logo
