Re: [Cython] memoryview slices can't be None?

2012-02-02 Thread mark florisson
On 2 February 2012 21:38, Dag Sverre Seljebotn wrote: > On 02/02/2012 10:16 PM, mark florisson wrote: >> >> On 2 February 2012 12:19, Dag Sverre Seljebotn >>  wrote: >>> >>> I just realized that >>> >>> cdef int[:] a = None >>> >>> raises an exception; even though I'd argue that 'a' is of the "re

Re: [Cython] memoryview slices can't be None?

2012-02-02 Thread Dag Sverre Seljebotn
On 02/02/2012 10:16 PM, mark florisson wrote: On 2 February 2012 12:19, Dag Sverre Seljebotn wrote: I just realized that cdef int[:] a = None raises an exception; even though I'd argue that 'a' is of the "reference" kind of type where Cython usually allow None (i.e., "cdef MyClass b = None"

Re: [Cython] memoryview slices can't be None?

2012-02-02 Thread mark florisson
On 2 February 2012 12:19, Dag Sverre Seljebotn wrote: > I just realized that > > cdef int[:] a = None > > raises an exception; even though I'd argue that 'a' is of the "reference" > kind of type where Cython usually allow None (i.e., "cdef MyClass b = None" > is allowed even if type(None) is NoneT

Re: [Cython] [cython-users] Re: How to find out where an AttributeError is ignored

2012-02-02 Thread mark florisson
On 1 February 2012 18:50, Robert Bradshaw wrote: > On Tue, Jan 31, 2012 at 8:30 AM, mark florisson > wrote: >> On 31 January 2012 02:12, Robert Bradshaw >> wrote: >>> On Fri, Jan 27, 2012 at 1:01 PM, Stefan Behnel wrote: Dag Sverre Seljebotn, 27.01.2012 21:03: > On 01/27/2012 05:58 PM

[Cython] memoryview slices can't be None?

2012-02-02 Thread Dag Sverre Seljebotn
I just realized that cdef int[:] a = None raises an exception; even though I'd argue that 'a' is of the "reference" kind of type where Cython usually allow None (i.e., "cdef MyClass b = None" is allowed even if type(None) is NoneType). Is this a bug or not, and is it possible to do something

[Cython] Cython's view on a common benchmark suite (was: Re: [Speed] Buildbot Status)

2012-02-02 Thread Stefan Behnel
Brett Cannon, 01.02.2012 18:25: > to prevent this from either ending up in a dead-end because of this, we > need to first decide where the canonical set of Python VM benchmarks are > going to live. I say hg.python.org/benchmarks for two reasons. One is that > Antoine has already done work there to