Re: [Cython] Cython Debian builds - failing cygdb tests

2012-08-09 Thread Stefan Behnel
Hi, Yaroslav Halchenko retried the test run on Sparc and all code related bugs seem to be resolved now (I had to fix a few minor endianess bugs). However, the cygdb tests still fail, but do not lead to a test run failure. Yaroslav Halchenko, 10.08.2012 01:05: > tested current 0.16rc1-591-g5de843

[Cython] Bitey

2012-08-09 Thread Dag Sverre Seljebotn
https://github.com/dabeaz/bitey Dag -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel

Re: [Cython] remaining open issues for 0.17

2012-08-09 Thread Yaroslav Halchenko
On Thu, 09 Aug 2012, Stefan Behnel wrote: > > Is it bad to release something that doesn't pass the entire test suite > > on some system? > Given that we already made tons of releases without even knowing that > they'd fail on some systems, I'd say no. :) FWIW -- some time ago 0.15.1 build/passe

Re: [Cython] remaining open issues for 0.17

2012-08-09 Thread Yaroslav Halchenko
FWIW -- just double checked -- tests pass (of current master) just fine on an i386 Debian system. On Thu, 09 Aug 2012, Yaroslav Halchenko wrote: > On Thu, 09 Aug 2012, Stefan Behnel wrote: > > > I thought the 32 bit issue was resolved? You pushed a fix and I fixed > > > some tests, so it passed f

Re: [Cython] remaining open issues for 0.17

2012-08-09 Thread Stefan Behnel
mark florisson, 09.08.2012 18:51: > On 9 August 2012 16:36, Stefan Behnel wrote: >> Stefan Behnel, 09.08.2012 14:31: >>> mark florisson, 07.08.2012 11:09: I thought the 32 bit issue was resolved? You pushed a fix and I fixed some tests, so it passed for me. I can run it again to check...

Re: [Cython] remaining open issues for 0.17

2012-08-09 Thread mark florisson
On 9 August 2012 16:36, Stefan Behnel wrote: > Stefan Behnel, 09.08.2012 14:31: >> mark florisson, 07.08.2012 11:09: >>> I thought the 32 bit issue was resolved? You pushed a fix and I fixed >>> some tests, so it passed for me. I can run it again to check... >> >> I don't know. Yaroslav replied to

Re: [Cython] remaining open issues for 0.17

2012-08-09 Thread Stefan Behnel
Stefan Behnel, 09.08.2012 14:31: > mark florisson, 07.08.2012 11:09: >> I thought the 32 bit issue was resolved? You pushed a fix and I fixed >> some tests, so it passed for me. I can run it again to check... > > I don't know. Yaroslav replied to your mail saying that your fixes didn't > change an

Re: [Cython] remaining open issues for 0.17

2012-08-09 Thread Yaroslav Halchenko
On Thu, 09 Aug 2012, Stefan Behnel wrote: > > I thought the 32 bit issue was resolved? You pushed a fix and I fixed > > some tests, so it passed for me. I can run it again to check... > I don't know. Yaroslav replied to your mail saying that your fixes didn't > change anything for the Debian build

Re: [Cython] remaining open issues for 0.17

2012-08-09 Thread Stefan Behnel
mark florisson, 07.08.2012 11:09: > I thought the 32 bit issue was resolved? You pushed a fix and I fixed > some tests, so it passed for me. I can run it again to check... I don't know. Yaroslav replied to your mail saying that your fixes didn't change anything for the Debian builds. Let's see wha

Re: [Cython] automatically raise MemoryError on exceptional C return values

2012-08-09 Thread Robert Bradshaw
On Wed, Aug 8, 2012 at 10:12 PM, Stefan Behnel wrote: > Robert Bradshaw, 09.08.2012 01:45: >> On Tue, Aug 7, 2012 at 2:53 AM, Stefan Behnel wrote: >>> given how ubiquitous manual memory management is in C, I think it would be >>> nice to let Cython generate the exception raising also for C, not on