I'm going to be tagging the tree for the NumPy 1.0.2 release tomorrow
evening in preparation for the release on Monday. I've closed several
bugs. Are there any show-stoppers remaining to be fixed?
-Travis
___
Numpy-discussion mailing list
Numpy-di
Another rather old ticket is this one:
http://projects.scipy.org/scipy/numpy/ticket/454>
Any comments on this !?
Thanks,
-Sebastian
On 2/16/07, NumPy <[EMAIL PROTECTED]> wrote:
> #454: Importing numpy prevents decrementing references for local variables
> +-
Hi!
Could someone comment on ticket #450
[Numpy-tickets] [NumPy] #450: Make a.min() not copy data
It seems odd that calculating the min of an array causes a memory error.
The demonstrated data array is a 3D cube of uint8 and about 1GB in size.
even creation of an extra (2d) array when reducing th
>
> I'm positive I've seen col * row come up in other contexts too, though
> I can't think of any other particulars right now.
>
Add to that quasi-Newton updates for quadratic models in optimization,
like the BFGS.
Paulo
___
Numpy-discussion mailing
