Re: [Cython] Cython 0.15 release candidate

2011-07-29 Thread Dag Sverre Seljebotn
Looks very much like a numpy-on-py3 bug to me. (NumPy has an RC up currently as well, it'd be good to test them together but don't think I have time this weekend...) Do you know if the problem is there with Cython 0.14? Even if not, it could simply be that the test cases now exercise more of Nu

Re: [Cython] Cython 0.15 release candidate

2011-07-29 Thread Arfrever Frehtes Taifersar Arahesis
2011-07-29 20:51:11 mark florisson napisał(a): > On 29 July 2011 19:18, Arfrever Frehtes Taifersar Arahesis > wrote: > > 2011-07-26 13:00:10 mark florisson napisał(a): > >> Unfortunately the output of the testrunner is rather useless here. > >> Could you run the tests with --no-cleanup and attach

Re: [Cython] Cython 0.15 release candidate

2011-07-29 Thread Robert Bradshaw
On Fri, Jul 29, 2011 at 11:24 AM, mark florisson wrote: > On 29 July 2011 20:06, Robert Bradshaw wrote: >> On Fri, Jul 29, 2011 at 1:33 AM, mark florisson >> wrote: >>> On 25 July 2011 08:03, Arfrever Frehtes Taifersar Arahesis >>> wrote: There are 4 test failures with Python 2.6, 2.7, 3.1

Re: [Cython] Cython 0.15 release candidate

2011-07-29 Thread mark florisson
On 29 July 2011 19:18, Arfrever Frehtes Taifersar Arahesis wrote: > 2011-07-26 13:00:10 mark florisson napisał(a): >> Unfortunately the output of the testrunner is rather useless here. >> Could you run the tests with --no-cleanup and attach the .c and .cpp >> files (found in build/run/c/numpy_cimp

Re: [Cython] Cython 0.15 release candidate

2011-07-29 Thread mark florisson
On 29 July 2011 20:06, Robert Bradshaw wrote: > On Fri, Jul 29, 2011 at 1:33 AM, mark florisson > wrote: >> On 25 July 2011 08:03, Arfrever Frehtes Taifersar Arahesis >> wrote: >>> There are 4 test failures with Python 2.6, 2.7, 3.1 and 3.2. >>> Output with Python 2.7: >>> >>> ==

Re: [Cython] Should we drop support for CPython 2.3? (and maybe even 2.4?)

2011-07-29 Thread Robert Bradshaw
On Wed, Jul 27, 2011 at 11:32 PM, Vitja Makarov wrote: > 2011/7/28 Stefan Behnel : >> Robert Bradshaw, 27.07.2011 20:28: >>> >>> Yes, that is a good point, though if it's (really) easy, I'd rather >>> say "this is the last release supporting 2.3" rather than "oh, btw, we >>> dropped support for 2.

Re: [Cython] Cython 0.15 release candidate

2011-07-29 Thread Robert Bradshaw
On Fri, Jul 29, 2011 at 1:33 AM, mark florisson wrote: > On 25 July 2011 08:03, Arfrever Frehtes Taifersar Arahesis > wrote: >> There are 4 test failures with Python 2.6, 2.7, 3.1 and 3.2. >> Output with Python 2.7: >> >> == >> F

Re: [Cython] Cython 0.15 release candidate

2011-07-29 Thread Arfrever Frehtes Taifersar Arahesis
2011-07-26 13:00:10 mark florisson napisał(a): > Unfortunately the output of the testrunner is rather useless here. > Could you run the tests with --no-cleanup and attach the .c and .cpp > files (found in build/run/c/numpy_cimport.c, etc)? I think something > is up with your numpy version and heade

Re: [Cython] GCC 4.6 unused-but-set-variable warnings

2011-07-29 Thread Stefan Behnel
Vitja Makarov, 29.07.2011 10:55: 2011/7/29 Stefan Behnel: Vitja Makarov, 29.07.2011 10:44: 2011/7/29 Stefan Behnel: Vitja Makarov, 29.07.2011 10:08: this issue isn't critical and even isn't a bug at all. Agreed. It's nothing that needs to be done for 0.15. I just thought you might be int

Re: [Cython] GCC 4.6 unused-but-set-variable warnings

2011-07-29 Thread Vitja Makarov
2011/7/29 Stefan Behnel : > Vitja Makarov, 29.07.2011 10:44: >> >> 2011/7/29 Stefan Behnel: >>> >>> Vitja Makarov, 29.07.2011 10:08: this issue isn't critical and even isn't a bug at all. >>> >>> Agreed. It's nothing that needs to be done for 0.15. I just thought you >>> might be interest

Re: [Cython] GCC 4.6 unused-but-set-variable warnings

2011-07-29 Thread Stefan Behnel
Vitja Makarov, 29.07.2011 10:44: 2011/7/29 Stefan Behnel: Vitja Makarov, 29.07.2011 10:08: this issue isn't critical and even isn't a bug at all. Agreed. It's nothing that needs to be done for 0.15. I just thought you might be interested. :D Yeah, I tried to do this once but I've found so

Re: [Cython] GCC 4.6 unused-but-set-variable warnings

2011-07-29 Thread Vitja Makarov
2011/7/29 Stefan Behnel : > Vitja Makarov, 29.07.2011 10:08: >> >> this issue isn't critical and even isn't a bug at all. > > Agreed. It's nothing that needs to be done for 0.15. I just thought you > might be interested. :D > Yeah, I tried to do this once but I've found some problems with buffer v

Re: [Cython] Cython 0.15 release candidate

2011-07-29 Thread mark florisson
On 25 July 2011 08:03, Arfrever Frehtes Taifersar Arahesis wrote: > There are 4 test failures with Python 2.6, 2.7, 3.1 and 3.2. > Output with Python 2.7: > > == > FAIL: test_nested_break_continue (line 331) (parallel.__test__) >

Re: [Cython] GCC 4.6 unused-but-set-variable warnings

2011-07-29 Thread Stefan Behnel
Vitja Makarov, 29.07.2011 10:08: this issue isn't critical and even isn't a bug at all. Agreed. It's nothing that needs to be done for 0.15. I just thought you might be interested. :D Stefan ___ cython-devel mailing list cython-devel@python.org htt

Re: [Cython] GCC 4.6 unused-but-set-variable warnings

2011-07-29 Thread Vitja Makarov
2011/7/29 Stefan Behnel : > Vitja Makarov, 29.07.2011 08:38: >> >> 2011/7/29 Vitja Makarov: >>> >>> 2011/7/29 Stefan Behnel: Nikolaus Rath, 13.06.2011 16:59: > > $ gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -fPIC -I/usr/include/python