Re: [Cython] Bug in Cython producing incorrect C code

2012-01-25 Thread Vitja Makarov
2012/1/25 Stefan Behnel : > mark florisson, 24.01.2012 14:53: >> On 24 January 2012 11:37, Konrad Hinsen wrote: >>> Compiling the attached Cython file produced the attached C file which >>> has errors in lines 532-534: >>> >>>  __pyx_v_self->xx = None; >>>  __pyx_v_self->yy = None; >>>  __pyx_v_sel

Re: [Cython] 0.16 release

2012-01-25 Thread Jason Grout
On 1/25/12 11:39 AM, Robert Bradshaw wrote: install https://sage.math.washington.edu:8091/hudson/view/ext-libs/job/sage-build/lastSuccessfulBuild/artifact/cython-devel.spkg by downloading it and running "sage -i cython-devel.spkg" In fact, you could just do sage -i https://sage.math.washingt

Re: [Cython] 0.16 release

2012-01-25 Thread Robert Bradshaw
On Wed, Jan 25, 2012 at 4:17 AM, mark florisson wrote: > On 25 January 2012 12:00, Stefan Behnel wrote: >> mark florisson, 25.01.2012 11:43: >>> On 25 January 2012 01:27, Robert Bradshaw wrote: On Mon, Jan 23, 2012 at 2:27 AM, mark florisson wrote: > It's been almost three months since w

Re: [Cython] 0.16 release

2012-01-25 Thread mark florisson
On 25 January 2012 12:00, Stefan Behnel wrote: > mark florisson, 25.01.2012 11:43: >> On 25 January 2012 01:27, Robert Bradshaw wrote: >>> On Mon, Jan 23, 2012 at 2:27 AM, mark florisson wrote: It's been almost three months since we talked about a 0.16 release, I think it's quite ready.

Re: [Cython] inline defnode calls

2012-01-25 Thread Stefan Behnel
mark florisson, 25.01.2012 12:36: > On 25 January 2012 11:32, mark florisson wrote: >> On 25 January 2012 11:24, Vitja Makarov wrote: >>> I'm thinking about implementing "conditional inlining": depending on >>> what function actually is it'll make direct call to C function or >>> PyObject_Call().

Re: [Cython] 0.16 release

2012-01-25 Thread Stefan Behnel
mark florisson, 25.01.2012 11:43: > On 25 January 2012 01:27, Robert Bradshaw wrote: >> On Mon, Jan 23, 2012 at 2:27 AM, mark florisson wrote: >>> It's been almost three months since we talked about a 0.16 release, I >>> think it's quite ready. It would already be a big release, it would be >>> goo

Re: [Cython] inline defnode calls

2012-01-25 Thread mark florisson
On 25 January 2012 11:32, mark florisson wrote: > On 25 January 2012 11:24, Vitja Makarov wrote: >> 2012/1/25 mark florisson : >>> On 25 January 2012 06:49, Vitja Makarov wrote: 2012/1/25 mark florisson : > I just noticed the inline defnode call code. When I try to compile > with 'c

Re: [Cython] inline defnode calls

2012-01-25 Thread mark florisson
On 25 January 2012 11:24, Vitja Makarov wrote: > 2012/1/25 mark florisson : >> On 25 January 2012 06:49, Vitja Makarov wrote: >>> 2012/1/25 mark florisson : I just noticed the inline defnode call code. When I try to compile with 'cython -Xoptimize.inline_defnode_calls=True test.pyx' wit

Re: [Cython] inline defnode calls

2012-01-25 Thread Vitja Makarov
2012/1/25 mark florisson : > On 25 January 2012 06:49, Vitja Makarov wrote: >> 2012/1/25 mark florisson : >>> I just noticed the inline defnode call code. When I try to compile >>> with 'cython -Xoptimize.inline_defnode_calls=True test.pyx' with the >>> following code: >>> >>> def foo(x): print fo

Re: [Cython] inline defnode calls

2012-01-25 Thread mark florisson
On 25 January 2012 06:49, Vitja Makarov wrote: > 2012/1/25 mark florisson : >> I just noticed the inline defnode call code. When I try to compile >> with 'cython -Xoptimize.inline_defnode_calls=True test.pyx' with the >> following code: >> >> def foo(x): print foo >> foo(10) >> >> I get >> >> Erro

Re: [Cython] 0.16 release

2012-01-25 Thread mark florisson
On 25 January 2012 01:27, Robert Bradshaw wrote: > On Mon, Jan 23, 2012 at 2:27 AM, mark florisson > wrote: >> Hey, >> >> It's been almost three months since we talked about a 0.16 release, I >> think it's quite ready. It would already be a big release, it would be >> good to see how people like

Re: [Cython] Bug in Cython producing incorrect C code

2012-01-25 Thread Stefan Behnel
mark florisson, 24.01.2012 21:28: > I must say though, the following would look a bit weird: > > a = b[:] = c[:, :] = d > > as you always expect a kind of "cascade", e.g. you expect c[:, :] to > be assignable to b[:], or 'a', but none of that may be true at all. That's normal for a typed lan

Re: [Cython] Bug in Cython producing incorrect C code

2012-01-25 Thread Dag Sverre Seljebotn
On 01/25/2012 07:59 AM, Vitja Makarov wrote: 2012/1/25 mark florisson: On 24 January 2012 19:18, Dag Sverre Seljebotn wrote: On 01/24/2012 08:05 PM, Vitja Makarov wrote: 2012/1/24 mark florisson: On 24 January 2012 18:30, Vitja Makarovwrote: 2012/1/24 Robert Bradshaw: On Tue, Jan