Re: [Cython] Cython-0.23.4 build failing on gcc6 for upcoming fedora 24

2016-02-07 Thread Dimitri John Ledkov
On 6 February 2016 at 17:46, Neal Becker  wrote:
> Robert Bradshaw wrote:
>
>> ==
>> FAIL: runTest (__main__.EndToEndTest)
>> End-to-end asyncio_generators
>> --
>> Traceback (most recent call last):
>>   File "runtests.py", line 1417, in runTest
>> self.assertEqual(0, res, "non-zero exit status")
>> AssertionError: 0 != 1 : non-zero exit status
>> --
>>
>> Not sure about this one (especially why it would be compiler dependent).
>>
>>
>> On Fri, Feb 5, 2016 at 6:15 PM, Neal Becker
>>  wrote:
>>> Robert Bradshaw wrote:
>>>
 Oh, I see what the issue is. Sorry. Try this (on top of the previous):

>>>
> https://github.com/cython/cython/commit/a2bec15e0db9ebdd22504268c15bfa059b44f72f

 On Fri, Feb 5, 2016 at 6:37 AM, Neal Becker
  wrote:
> Dimitri John Ledkov wrote:
>
>> On 5 February 2016 at 12:13, Neal Becker
>>  wrote:
>>> Robert Bradshaw wrote:
>>>
 Try this:

>>>
>
>>>
> https://github.com/cython/cython/commit/bd43a6a2c93443792d07caeb9647eab5a75858b7
>>>
>>> What's the easiest way to grab this in the form of a diff?  I don't
>>> see anything in the ui on github to do this (other than cut + paste +
>>> manually edit)
>>>
>>
>> Append .patch to get a wgetable git format-patch formated patch. So:
>>
>>
>
>>>
> https://github.com/cython/cython/commit/bd43a6a2c93443792d07caeb9647eab5a75858b7.patch
>>
>> Should be what you are after.
>>
>
> Better I suppose, now there is just 1 error:
>
> compiling (cpp) and running complex_numbers_c89_T398
>
> https://kojipkgs.fedoraproject.org//work/tasks/3468/12893468/build.log
>
> ___
> cython-devel mailing list
> cython-devel@python.org
> https://mail.python.org/mailman/listinfo/cython-devel
>>>
>>> Much better, but still 1 more problem:
>>> https://kojipkgs.fedoraproject.org//work/tasks/4695/12894695/build.log
>>>
>>> But it did complete build on my fedora 23 x86_64 laptop, the only diff
>>> should be gcc6.
>
> I disabled tests for python3 again - the async test also failed before.
> Maybe something to do with the testing environment.
>

async tests are failing with async module from python 3.5.1+

In ubuntu, i've disabled just those. Reported both to cython and async
upstream. Looks like not fixed yet.

-- 
Regards,

Dimitri.
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel


Re: [Cython] Cython-0.23.4 build failing on gcc6 for upcoming fedora 24

2016-02-07 Thread Neal Becker
Dimitri John Ledkov wrote:

> On 6 February 2016 at 17:46, Neal Becker
>  wrote:
>> Robert Bradshaw wrote:
>>
>>> ==
>>> FAIL: runTest (__main__.EndToEndTest)
>>> End-to-end asyncio_generators
>>> --
>>> Traceback (most recent call last):
>>>   File "runtests.py", line 1417, in runTest
>>> self.assertEqual(0, res, "non-zero exit status")
>>> AssertionError: 0 != 1 : non-zero exit status
>>> --
>>>
>>> Not sure about this one (especially why it would be compiler dependent).
>>>
>>>
>>> On Fri, Feb 5, 2016 at 6:15 PM, Neal Becker
>>>  wrote:
 Robert Bradshaw wrote:

> Oh, I see what the issue is. Sorry. Try this (on top of the previous):
>

>> 
https://github.com/cython/cython/commit/a2bec15e0db9ebdd22504268c15bfa059b44f72f
>
> On Fri, Feb 5, 2016 at 6:37 AM, Neal Becker
>  wrote:
>> Dimitri John Ledkov wrote:
>>
>>> On 5 February 2016 at 12:13, Neal Becker
>>>  wrote:
 Robert Bradshaw wrote:

> Try this:
>

>>

>> 
https://github.com/cython/cython/commit/bd43a6a2c93443792d07caeb9647eab5a75858b7

 What's the easiest way to grab this in the form of a diff?  I don't
 see anything in the ui on github to do this (other than cut + paste
 + manually edit)

>>>
>>> Append .patch to get a wgetable git format-patch formated patch. So:
>>>
>>>
>>

>> 
https://github.com/cython/cython/commit/bd43a6a2c93443792d07caeb9647eab5a75858b7.patch
>>>
>>> Should be what you are after.
>>>
>>
>> Better I suppose, now there is just 1 error:
>>
>> compiling (cpp) and running complex_numbers_c89_T398
>>
>> 
https://kojipkgs.fedoraproject.org//work/tasks/3468/12893468/build.log
>>
>> ___
>> cython-devel mailing list
>> cython-devel@python.org
>> https://mail.python.org/mailman/listinfo/cython-devel

 Much better, but still 1 more problem:
 https://kojipkgs.fedoraproject.org//work/tasks/4695/12894695/build.log

 But it did complete build on my fedora 23 x86_64 laptop, the only diff
 should be gcc6.
>>
>> I disabled tests for python3 again - the async test also failed before.
>> Maybe something to do with the testing environment.
>>
> 
> async tests are failing with async module from python 3.5.1+
> 
> In ubuntu, i've disabled just those. Reported both to cython and async
> upstream. Looks like not fixed yet.
> 
How can I disable just those?  Do you have a patch?

___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel


Re: [Cython] Cython-0.23.4 build failing on gcc6 for upcoming fedora 24

2016-02-07 Thread Todd Rme
On Feb 7, 2016 9:02 AM, "Dimitri John Ledkov"  wrote:
>
> On 6 February 2016 at 17:46, Neal Becker  wrote:
> >
> > I disabled tests for python3 again - the async test also failed before.
> > Maybe something to do with the testing environment.
> >
>
> async tests are failing with async module from python 3.5.1+
>
> In ubuntu, i've disabled just those. Reported both to cython and async
> upstream. Looks like not fixed yet.

For openSUSE I am still holding out for a proper fix (although I am not
sure how much longer we can put things off).  I consider the failure to be
a serious one.

The tests are failing because the new await command doesn't return anything
in cython with python 3.5.1+, although it works fine in ordinary python
cython under python 3.5.0.  This can lead to subtle failures in code,
depending on what sort of return values the code is prepared for.
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel


Re: [Cython] Cython-0.23.4 build failing on gcc6 for upcoming fedora 24

2016-02-07 Thread Stefan Behnel
Robert Bradshaw schrieb am 06.02.2016 um 09:24:
> ==
> FAIL: runTest (__main__.EndToEndTest)
> End-to-end asyncio_generators
> --
> Traceback (most recent call last):
>   File "runtests.py", line 1417, in runTest
> self.assertEqual(0, res, "non-zero exit status")
> AssertionError: 0 != 1 : non-zero exit status
> --
> 
> Not sure about this one (especially why it would be compiler dependent).

It's not compiler dependent. It's an incompatibility between Cython and
CPython's asyncio. Might be related to the fact that asyncio's Future is
both iterable and awaitable. Or something else... I looked into it but
couldn't figure it out yet.

Stefan

___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel


Re: [Cython] import-free setuptools integration

2016-02-07 Thread Greg Ewing

Nils Werner wrote:
 - Having `cythonize()` internally automatically compile *.pyx files 
when *.c files
   are provided is disabled by default and must be enabled using the 
`replace_extension`

   keyword argument (`cython_modules` enables that option).


I'd be happier if it were still disabled by default even then.
If I'm simply installing a package, I do *not* want it to
try to recompile any .pyx files just because I happen to have
cython installed.

I know that isn't supposed to happen unless the .pyx is newer
than the .c, but I wouldn't like to rely on that. There's a
big difference between using a package and modifying it, and
I'd rather be explicit about when I'm doing the latter.

--
Greg
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel