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
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:
Is this a bug?
In [81]: a = np.dtype([('field', 'u1', (2**31,))])
In [82]: a.itemsize
Out[82]: -2147483648
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Any chance of getting this into the next release?
http://projects.scipy.org/scipy/ticket/1122
I marked it 0.8 because that was the default, but it is a very simple fix.
Russel
Sebastian Haase wrote:
> Hi Ralf,
> congratulation to the new RC.
> Just for the record, where did you ann
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
>
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
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.
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
t)
/Users/baxter/ in ()
MemoryError: cannot allocate array memory
I am not sure how to include a test whose failure condition is the
raising of an exception, but the patch includes the above test.
Russel
Index: numpy/core/src/multiarr
ince most seem to return an empty array now.
Russel
they're all fine hovses.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
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)
>>>
11 matches
Mail list logo
