Neal Becker wrote:
> Jon Wright wrote:
>
>>> I'm sorry, I still think we're talking past each other. What do you mean
>>> by "native data type"? If you just want to get an ndarray without
>>> specifying a type, use PyArray_FROM_O(). That's what it's for. You don't
>>> need to know the data type be
Hi,
> We talked about this at the SciPy Sprint. Eventually, we will get
> there. However, if we do it before 1.0.5, it will require nose to run
> the NumPy tests. I'm concerned to make this kind of change, prior to 1.1
Ah, sorry, I heard of the conclusion, but had thought it was due to
the 2.
Neal Becker wrote:
> Robert Kern wrote:
>
>> Neal Becker wrote:
>>> I've never liked that python silently ignores slices with out of range
>>> indexes. I believe this is a source of bugs (it has been for me). It
>>> goes completely counter to the python philosophy.
>>>
>>> I vote to ban them fro
On Jan 14, 2008 12:37 PM, Neal Becker <[EMAIL PROTECTED]> wrote:
> I've never liked that python silently ignores slices with out of range
> indexes. I believe this is a source of bugs (it has been for me). It
> goes
> completely counter to the python philosophy.
>
> I vote to ban them from numpy
Matthew Brett wrote:
> Hi,
>
> I've just finished moving the scipy tests over to nose.
>
> Thinking about it, it seems to me to be a good idea to do the same for numpy.
>
We talked about this at the SciPy Sprint. Eventually, we will get
there. However, if we do it before 1.0.5, it will requir
Robert Kern wrote:
> Neal Becker wrote:
>> I've never liked that python silently ignores slices with out of range
>> indexes. I believe this is a source of bugs (it has been for me). It
>> goes completely counter to the python philosophy.
>>
>> I vote to ban them from numpy.
> from numpy im
An added advantage is that is makes it much easier to run doctests:
numpy.test(doctests=True)
On Jan 14, 2008 11:36 AM, Fernando Perez <[EMAIL PROTECTED]> wrote:
> On Jan 14, 2008 5:21 AM, Matthew Brett <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I've just finished moving the scipy tests over to
Neal Becker wrote:
> I've never liked that python silently ignores slices with out of range
> indexes. I believe this is a source of bugs (it has been for me). It goes
> completely counter to the python philosophy.
>
> I vote to ban them from numpy.
from numpy import array
x = array (x
I've never liked that python silently ignores slices with out of range
indexes. I believe this is a source of bugs (it has been for me). It goes
completely counter to the python philosophy.
I vote to ban them from numpy.
>>> from numpy import array
>>> x = array (xrange (10))
>>> x[11]
Traceback
On Jan 14, 2008 5:21 AM, Matthew Brett <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've just finished moving the scipy tests over to nose.
>
> Thinking about it, it seems to me to be a good idea to do the same for numpy.
> Any thoughts?
A big +1 from me.
Cheers,
f
_
Jon Wright wrote:
>> I'm sorry, I still think we're talking past each other. What do you mean
>> by "native data type"? If you just want to get an ndarray without
>> specifying a type, use PyArray_FROM_O(). That's what it's for. You don't
>> need to know the data type beforehand.
>
> What I have
> I'm sorry, I still think we're talking past each other. What do you mean by
> "native data type"? If you just want to get an ndarray without specifying a
> type, use PyArray_FROM_O(). That's what it's for. You don't need to know the
> data type beforehand.
What I have wanted in the past (and
Neal Becker wrote:
> Robert Kern wrote:
>
>> Neal Becker wrote:
>>> numpy frequently refers to 'casting'. I'm not sure if that term is ever
>>> defined. I believe it has the same meaning as in C. In that case, it is
>>> unfortunately used to mean 2 different things. There are casts that do
>>>
Hi,
I've just finished moving the scipy tests over to nose.
Thinking about it, it seems to me to be a good idea to do the same for numpy.
The advantages of doing this now are that numpy and scipy would be in
parallel, that we can continue to have one testing system for both,
and that it would be
Robert Kern wrote:
> Neal Becker wrote:
>> numpy frequently refers to 'casting'. I'm not sure if that term is ever
>> defined. I believe it has the same meaning as in C. In that case, it is
>> unfortunately used to mean 2 different things. There are casts that do
>> not change the underlying b
Matthew Brett wrote:
> Hi,
>
>
>> A quick email to give an update on my work to build numpy with
>> scons. I've finished a few days ago to make my former work a separate
>> package from numpy: it was more work than I expected because of
>> bootstrapping issues, but I can now build numpy agai
16 matches
Mail list logo
