On 8/17/07, Barry Wark <[EMAIL PROTECTED]> wrote:
>
> Is there a reason not to add an argument to fromiter that specifies
> the final size of the n-d array? Reading this discussion, I realized
> that there are several places in my code where I create 2-D arrays
> like this:
>
> arr = N.array([d.dat
Is there a reason not to add an argument to fromiter that specifies
the final size of the n-d array? Reading this discussion, I realized
that there are several places in my code where I create 2-D arrays
like this:
arr = N.array([d.data() for d in list_of_data_containers]),
where d.data() returns
On 8/17/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Geoffrey Zhu wrote:
> > Hi All,
> >
> > I want to construct a numpy array based on Python objects. In the
> > below code, opts is a list of tuples.
> >
> > For example,
> >
> > opts=[ ('C', 100, 3, 'A'), ('K', 200, 5.4, 'B')]
> >
> > If I use a g
Hi,
I noticed that allclose does not always behave correctly for arrays with infs.
I've attached a test script for allclose, and here's an alternative
implementation that I believe behaves correctly.
Obviously the test script could be a test case in core/tests/test_numeric.py
I wonder if we sho
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
