Mailman 3 January 2016 - cython-devel

cygdb: no debug files were found
by Nathan Goldbaum Sept. 14, 2016

Sept. 14, 2016

Hi all, I'm following the directions in the link below to debug some cython code using cygdb: http://docs.cython.org/src/userguide/debugging.html Unfortunately, when I try to actually debug my program using cygdb, I get a "no debug files were found" error. It looks like the error is getting raised here: https://github.com/cython/cython/blob/master/Cython/Debugger/Cygdb.py#L33 So for some reason the "cython_debug" folder isn't being generated at build time. I tried to follow the directions closely, you can see the notes I put together during the installation process here: https://bpaste.net/show/6b11f815d449 Unfortunately the library I'm trying to debug (yt: bitbucket.org/yt_analysis/yt) uses a somewhat nonstandard build setup based on numpy distutils, and I suspect that is breaking some of the assumptions that went into the cygdb instructions in the cython docs. Does anyone have any idea what went wrong here? For now I'm going to fall back to regular gdb, and debug the autogenerated cython sources. Thanks for your help, Nathan Goldbaum

2 1

Cython 0.23.4: Crash with Template Stuff
by Elizabeth Fischer Feb. 2, 2016

Feb. 2, 2016

Cython is crashing on me when I compile. See below. -- Elizabeth cython --version Cython version 0.23.4 Error compiling Cython file: ------------------------------------------------------------ ... # cdef int flags def test_double_blitz(a): cdef vector[int] v cdef cblitz.Array[double,1] a_b a_b = cibmisc.np_to_blitz[double,1](a, b'var', [-1]) ^ ------------------------------------------------------------ /Users/rpfische/git/ibmisc/pylib/ibmisc.pyx:38:26: Compiler crash in AnalyseExpressionsTransform ModuleNode.body = StatListNode(ibmisc.pyx:1:0) StatListNode.stats[3] = StatListNode(ibmisc.pyx:35:0) StatListNode.stats[0] = DefNode(ibmisc.pyx:35:0, modifiers = [...]/0, name = 'test_double_blitz', num_required_args = 1, py_wrapper_required = True, reqd_kw_flags_cname = '0', used = True) File 'Nodes.py', line 430, in analyse_expressions: StatListNode(ibmisc.pyx:36:1) File 'Nodes.py', line 4775, in analyse_expressions: SingleAssignmentNode(ibmisc.pyx:38:36) File 'Nodes.py', line 4887, in analyse_types: SingleAssignmentNode(ibmisc.pyx:38:36) File 'ExprNodes.py', line 4640, in analyse_types: SimpleCallNode(ibmisc.pyx:38:36, analysed = True, result_is_used = True, use_managed_ref = True) File 'ExprNodes.py', line 3109, in analyse_types: IndexNode(ibmisc.pyx:38:26, is_called = 1, is_subscript = True, result_is_used = True, use_managed_ref = True) File 'ExprNodes.py', line 3419, in analyse_base_and_index_types: IndexNode(ibmisc.pyx:38:26, is_called = 1, is_subscript = True, result_is_used = True, use_managed_ref = True) Compiler crash traceback from this point on: File "/Users/rpfische/macports/mpgompi-4.9.3/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/Cython/Compiler/ExprNodes.py", line 3419, in analyse_base_and_index_types elif len(base_type.templates) != len(self.type_indices): TypeError: object of type 'NoneType' has no len() make[2]: *** [pylib/ibmisc.cpp] Error 1 make[2]: *** Deleting file `pylib/ibmisc.cpp' make[1]: *** [pylib/CMakeFiles/ibmisc_so.dir/all] Error 2 make: *** [all] Error 2

3 4

cython 0.23.4 test failure, async_iter_pep492 (), asyncio_generators, test_async_def_future.py
by Todd Rme Jan. 20, 2016

Jan. 20, 2016

On 13 January 2016 at 17:50, Orion Poplawski <orion at <https://mail.python.org/mailman/listinfo/cython-devel> cora.nwra.com <https://mail.python.org/mailman/listinfo/cython-devel>> wrote: >* Dimitri John** Ledkov** <**xnox* <https://mail.python.org/mailman/listinfo/cython-devel>* at ...* <https://mail.python.org/mailman/listinfo/cython-devel>*> writes:* > >> >>* Hello,* >> >>* Building 0.23.4 fails on** ubuntu** with python 3.5.* >> >>* Full build log is at:* >> >* https* <https://launchpadlibrarian.net/228728126/buildlog_ubuntu-xenial>*://* <https://launchpadlibrarian.net/228728126/buildlog_ubuntu-xenial> *launchpadlibrarian.net* <https://launchpadlibrarian.net/228728126/buildlog_ubuntu-xenial> */228728126/* <https://launchpadlibrarian.net/228728126/buildlog_ubuntu-xenial>*buildlog* <https://launchpadlibrarian.net/228728126/buildlog_ubuntu-xenial>*_* <https://launchpadlibrarian.net/228728126/buildlog_ubuntu-xenial> *ubuntu-xenial* <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://* <https://kojipkgs.fedoraproject.org//work/tasks/5210/12535210/build.log> *kojipkgs.fedoraproject.org* <https://kojipkgs.fedoraproject.org//work/tasks/5210/12535210/build.log> *//work/tasks/5210/12535210/* <https://kojipkgs.fedoraproject.org//work/tasks/5210/12535210/build.log> *build.log* <https://kojipkgs.fedoraproject.org//work/tasks/5210/12535210/build.log> We are seeing the same failure on openSUSE, and I think I have worked out part of the reason why. I have been playing around with the failing unit test using travis and my own github fork. If I enable testing on python 3.5.1 or 3.5-dev the problem appears there too. Cython doesn't currently test against these, which is why the issue wasn't discovered earlier. I have discovered that the change in behaviour between 3.5 and 3.5.1 occurs in line 224 of cython/tests/run/asyncio_generators.srctree In this line, in python 3.5 the "await fut" statement returned the result of "fut", 123. In python 3.5.1+, however, it returns None instead. The result value is successfully getting set, as seen by checking "fut.get_result()" after the await, but the await is not returning it. You would think this would be an upstream Python problem, so I tried it in a standalone python interpreter. However, the problem didn't happen, it worked as it did in 3.5. So I went back to the test and changed the extension of "async_def_future" from "pyx" to "py" and the problem disappeared! So somehow cython is doing something different with await than normal python, and this is causing await to return None in python 3.5.1+. However, I do not know specifically what this is, or why it behaves differently in 3.5 and 3.5.1

1 0

cython 0.23.4 test failure, async_iter_pep492 (), asyncio_generators, test_async_def_future.py
by Dimitri John Ledkov Jan. 14, 2016

Jan. 14, 2016

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.cytho… First with 2.7, run.asyncio_generators are skipped. Then there is a successful run of asyncio_generators (?!) and then a failed one (?!) The what i think relevant portion of the build log is as follows: async_iter_pep492 () Doctest: async_iter_pep492 ... ok test_aiter_raises (async_iter_pep492) Doctest: async_iter_pep492.test_aiter_raises ... ok test_broken_anext (async_iter_pep492) Doctest: async_iter_pep492.test_broken_anext ... ok test_for_1 (async_iter_pep492) Doctest: async_iter_pep492.test_for_1 ... ok test_for_2 (async_iter_pep492) Doctest: async_iter_pep492.test_for_2 ... ok test_for_3 (async_iter_pep492) Doctest: async_iter_pep492.test_for_3 ... ok test_with_for (async_iter_pep492) Doctest: async_iter_pep492.test_with_for ... ok runTest (__main__.EndToEndTest) 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] ok Any help resolving this would help. Is this a broken python3.5? or cython? or both? -- Regards, Dimitri.

2 2

Cython creates non-pickleable classes
by Serhiy Storchaka Jan. 12, 2016

Jan. 12, 2016

Sorry, I'm not very familiar with Cython, but it looks to me that Cython creates extension classes that can't be correctly copied and unpickled. Since default __reduce_ex__ implementation knows nothing about Cython class structure, it's result doesn't contain the state of the object. The object could be pickled, but unpickled object doesn't contain original values of fields, it is just non-initialized. In recent CPython releases was added new restrictions for pickling objects that can't be correctly unpickled. This had added incompatibility with Cython classes. Building some packages now is failed, because Cython makes a deep copy that actually doesn't work. See for original changes and discussion about the regression: http://bugs.python.org/issue22995 . Besides the fact of Cython regression, it looks to me, that Cython also needs to be fixed. It can be done either by generating default pickle-related methods (__getnewargs__/__getnewargs_ex__, or __getstate__ + __setstate__, or __reduce__/__reduce_ex__) for all Cython classes, or implementing pickling or deepcopying only for NameAssignment and like.

2 1

strange error message
by B. Clausius Jan. 5, 2016

Jan. 5, 2016

Hi cython devs, a strange error message, showing cython internals: $ cat gldraw.pxd ctypedef float vec4[4] ctypedef vec4 mat4[4] $ cat glarea.pyx cimport gldraw cdef struct Data: gldraw.mat4 matrix cdef Data data cdef void sync(): data.changed = True # <- this wrong line produces the error $ cython glarea.pyx Error compiling Cython file: ------------------------------------------------------------ ... void PyTuple_SET_ITEM(object p, Py_ssize_t pos, object o) void PyList_SET_ITEM(object p, Py_ssize_t pos, object o) @cname("__Pyx_carray_to_py_vec4") cdef inline list __Pyx_carray_to_py_vec4(vec4 *v, Py_ssize_t length): ^ ------------------------------------------------------------ carray.to_py:112:41: 'vec4' is not a type identifier Error compiling Cython file: ------------------------------------------------------------ ... PyList_SET_ITEM(l, i, value) return l @cname("__Pyx_carray_to_tuple_vec4") cdef inline tuple __Pyx_carray_to_tuple_vec4(vec4 *v, Py_ssize_t length): ^ ------------------------------------------------------------ carray.to_py:124:45: 'vec4' is not a type identifier $ cython --version Cython version 0.23.3 Best regards, B.C.

3 5