Re: [Numpy-discussion] Memory Leak

2012-07-22 Thread Russel Howe
Never mind, this was fixed with commit 3a7e61c7d55be9a84929747c38cd71e62593129d. Russel From: numpy-discussion-boun...@scipy.org [numpy-discussion-boun...@scipy.org] on behalf of Russel Howe [rus...@appliedminds.com] Sent: Friday, July 20, 2012 8:04 PM

[Numpy-discussion] Memory Leak

2012-07-20 Thread Russel Howe
The attached program leaks about 24 bytes per loop. The comments give a bit more detail as to when the leak occurs and doesn't. How can I track down where this leak is actually coming from? Here is a sample run on my machine: $ python simple.py Python Version: 2.7.3 (default, Apr 20 2012, 22:

Re: [Numpy-discussion] Is this expected behavior?

2010-01-18 Thread Russel Howe
Oh, of course. I can reverse it myself. Thanks, I did not think of that. Russel Warren Weckesser wrote: > Russel Howe wrote: >> Since they are iterators, is it possible to check for the second >> condition and reverse both of them so the behavior I expect happens or >

Re: [Numpy-discussion] Is this expected behavior?

2010-01-18 Thread Russel Howe
Since they are iterators, is it possible to check for the second condition and reverse both of them so the behavior I expect happens or does this break something else? Russel Robert Kern wrote: > On Mon, Jan 18, 2010 at 13:41, Russel Howe wrote: >> This looks like the differenc

[Numpy-discussion] Is this expected behavior?

2010-01-18 Thread Russel Howe
This looks like the difference between memmove and memcpy to me, but I am not sure what the expected behavior of numpy should be. The first shift behaves the way I expect, the second is surprising. I know about numpy.roll. I was hoping for something faster, which this would be if it worked.

Re: [Numpy-discussion] bug in fromiter - with patch

2008-09-26 Thread Russel Howe
Oops. I made a last minute change without re-running the tests. The tests refer to np.range, that should just be range. Corrected test attached. Russel Howe wrote: As of SVN from this morning, fromiter cannot create an array whose dtype is a byte type In [1]: np.fromiter(range(10), dtype

[Numpy-discussion] bug in fromiter - with patch

2008-09-26 Thread Russel Howe
As of SVN from this morning, fromiter cannot create an array whose dtype is a byte type In [1]: np.fromiter(range(10), dtype='b') --- MemoryError Traceback (most recent call last) /Users/baxter

Re: [Numpy-discussion] Complex arange

2007-02-01 Thread Russel Howe
> arange(1j, 5j, 1) do? Numeric raises an exception here, and I thing > numpy > should, too. > The same as arange(1, 5, 1j) - an empty array since it takes 0 of the step to cross the distance. But something like arange(1j, 5j, 1j) seems fine. As does arange(1j, 3+5j, 2+1j) which should gi

[Numpy-discussion] Complex arange

2007-02-01 Thread Russel Howe
Should this work? Python 2.4.3 (#1, Dec 27 2006, 21:18:13) [GCC 4.0.1 (Apple Computer, Inc. build 5341)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import numpy as N >>> N.__version__ '1.0.2.dev3531' >>> N.arange(1j, 5j) array([], dtype=complex128) >>>