Re: [Numpy-discussion] 1.5 release schedule proposal

2010-07-27 Thread Jed Ludlow
On Tue, Jul 27, 2010 at 2:38 AM, Pauli Virtanen wrote: > > One low-hanging fruit to fix could be np.fromfile raising MemoryError > when it encounters EOF, and other bugs in that part of the code. The EOF bug in np.fromfile may already be fixed: http://projects.scipy.org/numpy/ticket/1152 unless

[Numpy-discussion] Meshgrid and mgrid Differences

2010-07-15 Thread Jed Ludlow
d in the scene by 90 degrees. Regards, Jed Ludlow ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Integer Overflow?

2009-07-14 Thread Jed Ludlow
Dave wrote: > I got stung when taking an ordinary python integer to the power of a numpy > integer - the result wasn't what I was expecting (see below)! From the results below, it seems to be okay if the base is a long. Note the type of the returned result in each case. Does it seem inconsiste

Re: [Numpy-discussion] fromfile and ticket #1152

2009-06-27 Thread Jed Ludlow
Charles R Harris gmail.com> writes: > > The question is: what should happen when fewer items are read than > requested. The current behaviour is > > 1) Error message written to stderr (needs to be fixed) > 2) If 0 items are read then nomemory error is raised ;) > > So, should a warning be rais