Re: [Cython] (no subject)

2012-12-10 Thread Yaroslav Halchenko
On Mon, 10 Dec 2012, Stefan Behnel wrote: > >> so how to make it 'effective'? > > no hints from the experts? ;) > Usually, running gc.collect() after this kind of test (i.e. as part of the > doctest) is a good way to provoke a crash in time. wasn't it obvious ? ;-) Thanks! https://github.com

Re: [Cython] (no subject)

2012-12-10 Thread Stefan Behnel
Yaroslav Halchenko, 10.12.2012 14:55: > On Wed, 05 Dec 2012, Yaroslav Halchenko wrote: >> On Wed, 05 Dec 2012, mark florisson wrote: Thanks, I merged it. > >>> It'd be nice if you could add this as a testcase in the tests/run >>> directory as a "don't segfault" kind of test. > >> I would be

Re: [Cython] (no subject)

2012-12-10 Thread Yaroslav Halchenko
On Wed, 05 Dec 2012, Yaroslav Halchenko wrote: > On Wed, 05 Dec 2012, mark florisson wrote: > > > Thanks, I merged it. > > It'd be nice if you could add this as a testcase in the tests/run > > directory as a "don't segfault" kind of test. > I would be happy to extend the test battery but my bl

Re: [Cython] (no subject)

2012-12-05 Thread Yaroslav Halchenko
On Wed, 05 Dec 2012, mark florisson wrote: > > Thanks, I merged it. > It'd be nice if you could add this as a testcase in the tests/run > directory as a "don't segfault" kind of test. I would be happy to extend the test battery but my blunt attempt failed, i.e. the test doesn't cause the failure

Re: [Cython] (no subject)

2012-12-05 Thread mark florisson
On 5 December 2012 17:11, mark florisson wrote: > On 5 December 2012 16:54, Yaroslav Halchenko wrote: >> Thank you Bradley, >> >> This was easy enough even so that I could fix it (I think) -- just a >> typo: >> >> https://github.com/cython/cython/pull/165 >> >> feedback would be welcome ;) >>

Re: [Cython] (no subject)

2012-12-05 Thread mark florisson
On 5 December 2012 16:54, Yaroslav Halchenko wrote: > Thank you Bradley, > > This was easy enough even so that I could fix it (I think) -- just a > typo: > > https://github.com/cython/cython/pull/165 > > feedback would be welcome ;) > > On Mon, 03 Dec 2012, Bradley M. Froehle wrote: > >>I

Re: [Cython] (no subject)

2012-12-05 Thread Yaroslav Halchenko
Thank you Bradley, This was easy enough even so that I could fix it (I think) -- just a typo: https://github.com/cython/cython/pull/165 feedback would be welcome ;) On Mon, 03 Dec 2012, Bradley M. Froehle wrote: >I ran `git bisect`: >d96dfdbb290d23bf3b4a186dc5b1b5d9ee7fcaa5 is the

Re: [Cython] (no subject)

2012-12-03 Thread Bradley M. Froehle
I ran `git bisect`: d96dfdbb290d23bf3b4a186dc5b1b5d9ee7fcaa5 is the first bad commit commit d96dfdbb290d23bf3b4a186dc5b1b5d9ee7fcaa5 Author: Mark Florisson Date: Tue Apr 10 15:01:00 2012 +0100 Decref memoryview slice class attributes https://github.com/cython/cython/commit/d96dfdbb290d23b

[Cython] (no subject)

2012-12-03 Thread Yaroslav Halchenko
reproduced with cython 0.17.2 (+ few post release fixes), originally detected/reported [1] with 0.17.1 on Debian systems using debug build of Python: $> python-dbg -c 'import pyximport as pi; pi.install(); import weakfail; s=weakfail.foo(42)'