On 13 January 2016 at 17:50, Orion Poplawski <or...@cora.nwra.com> wrote: > Dimitri John Ledkov <xnox@...> writes: > >> >> Hello, >> >> Building 0.23.4 fails on ubuntu with python 3.5. >> >> Full build log is at: >> > https://launchpadlibrarian.net/228728126/buildlog_ubuntu-xenial > -amd64.cython_0.23.4-0ubuntu1_BUILDING.txt.gz >> >> The what i think relevant portion of the build log is as follows: >> >> End-to-end asyncio_generators ... FAIL >> runTest (__main__.CythonRunTestCase) >> compiling (c) and running attr ... attr () >> Doctest: attr ... /usr/bin/python3.5 test_async_def_future.py >> >> Traceback (most recent call last): >> File "test_async_def_future.py", line 16, in <module> >> runloop() >> File "test_async_def_future.py", line 14, in runloop >> assert events == expected, events >> AssertionError: ['setup', 'setval', None] >> >> Any help resolving this would help. Is this a broken python3.5? or >> cython? or both? > > We are seeing the same thing building cython 0.23.4 on Fedora rawhide for > python 3.5.1: > > https://kojipkgs.fedoraproject.org//work/tasks/5210/12535210/build.log
I've also filed an issue against asyncio module on github, but i was redirected by to cypthon. https://github.com/python/asyncio/issues/308 On Ubuntu / Launchpad this is tracked here https://bugs.launchpad.net/ubuntu/+source/cython/+bug/1526613 Reverting the changes between 3.5.0 and 3.5.1 of the asyncio module alone, makes the cyphon test-suite pass again. But I cannot reproduce the thing being tested in a stand-alone scenario, to validate if it's cython that is depending on undefined behaviour and/or asyncio module has something broken. -- Regards, Dimitri. _______________________________________________ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
