[Cython] Cython alpha 0.24
We are getting ready to push a new major release. A first alpha is up at http://cython.org/release/Cython-0.24a0.tar.gz To avoid surprises, please test and report. Thanks, Robert ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Cython alpha 0.24
Hello, Is there any chance of merging https://github.com/cython/cython/pull/483 It is a really trivial patch. Thanks, Jeroen. ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Cython alpha 0.24
I'd really rather deprecate .pxi files completely rather than add even more support for them. I haven't dived into cysignals yet, but it seems it could be done with a cimport alone. On Fri, Mar 11, 2016 at 12:30 AM, Jeroen Demeyer wrote: > Hello, > > Is there any chance of merging https://github.com/cython/cython/pull/483 > It is a really trivial patch. > > Thanks, > Jeroen. > ___ > cython-devel mailing list > cython-devel@python.org > https://mail.python.org/mailman/listinfo/cython-devel ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
[Cython] Support for .pxi files
Dear Cython developers, I'm writing this in response to Robert's "I'd really rather deprecate .pxi files completely". Can you please explain what you have against .pxi files? I know they have been abused and 95% of the historic use cases should be replaced by other means. However, that alone is not sufficient reason to stop supporting them: there is still the 5% of cases where they are really useful. I think that you should continue to support .pxi files on a same level as .pxd files. I still do not understand why https://github.com/cython/cython/pull/392 was refused and it seems that https://github.com/cython/cython/pull/483 is going to be refused too. Jeroen Demeyer. ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Cython alpha 0.24
On 2016-03-11 10:00, Robert Bradshaw wrote: but it seems it could be done with a cimport alone. I already discussed that with Stefan Behnel... no, it cannot be done with a cimport alone. ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Support for .pxi files
On Fri, Mar 11, 2016 at 1:13 AM, Jeroen Demeyer wrote: > Dear Cython developers, > > I'm writing this in response to Robert's "I'd really rather deprecate .pxi > files completely". > > Can you please explain what you have against .pxi files? They're neither necessary nor pythonic. Even C++ is trying to move away from #includes to proper modules. On a more pragmatic note, includes add complexities to dependency tracking (among other things) and we still have cruft from abuse of pxi files, e.g. https://github.com/cython/cython/blob/16ad9e21da64c4de4f964980ad1b8c18ca70035b/Cython/Compiler/ExprNodes.py#L891 > I know they have > been abused and 95% of the historic use cases should be replaced by other > means. However, that alone is not sufficient reason to stop supporting them: > there is still the 5% of cases where they are really useful. Every single case I can think of would be better done by using cimports or preprocessing via a proper templating (or at least preprocessing) utility. Now cysignals is the kind of package that might be doing something tricky that makes this a special case, but even then I'd call that 0.5% not 5%. I need to dive into that deeper. > I think that you should continue to support .pxi files on a same level as > .pxd files. I still do not understand why > https://github.com/cython/cython/pull/392 was refused and it seems that > https://github.com/cython/cython/pull/483 is going to be refused too. > > Jeroen Demeyer. > ___ > cython-devel mailing list > cython-devel@python.org > https://mail.python.org/mailman/listinfo/cython-devel ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Support for .pxi files
On 2016-03-11 10:34, Robert Bradshaw wrote: On a more pragmatic note, includes add complexities to dependency tracking Because you *intentionally* make things complicated. The refused pull request 392 could actually make dependency checking simpler by treating .pxd and .pxi files more alike. Every single case I can think of would be better done by using cimports or preprocessing via a proper templating (or at least preprocessing) utility. The difference is that such preprocessing will be external to Cython, which will make the build process more complex. You need to figure out what to do with the files generated by the templating and you need to get dependency checking right... I must admit that I am quite happy that Cython solves these problems for me. Do you have an example of a project which actually uses such templating/preprocessing? Jeroen. ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Cython alpha 0.24
I get one testsuite failure: $ python runtests.py -v -v fused_cpp Python 2.7.10 (default, Mar 11 2016, 09:57:44) [GCC 4.8.4] Running tests against Cython 0.24a0 Backends: c,cpp runTest (__main__.CythonRunTestCase) compiling (cpp) and running fused_cpp ... === Expected errors: === === Got errors: === 14:16: Compiler crash in AnalyseDeclarationsTransform ERROR == ERROR: runTest (__main__.CythonRunTestCase) compiling (cpp) and running fused_cpp -- Traceback (most recent call last): File "runtests.py", line 993, in run ext_so_path = self.runCompileTest() File "runtests.py", line 705, in runCompileTest self.test_directory, self.expect_errors, self.annotate) File "runtests.py", line 928, in compile self.assertEquals(None, unexpected_error) AssertionError: None != u'14:16: Compiler crash in AnalyseDeclarationsTransform' -- Ran 1 test in 0.350s FAILED (errors=1) ALL DONE ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Cython alpha 0.24
https://github.com/cython/cython/commit/970c2fc0e676ca22016e14147ada0edba937dc6b (Just noticed the build failed on travis too...) On Fri, Mar 11, 2016 at 2:09 AM, Jeroen Demeyer wrote: > I get one testsuite failure: > > $ python runtests.py -v -v fused_cpp > Python 2.7.10 (default, Mar 11 2016, 09:57:44) > [GCC 4.8.4] > > Running tests against Cython 0.24a0 > Backends: c,cpp > > runTest (__main__.CythonRunTestCase) > compiling (cpp) and running fused_cpp ... > === Expected errors: === > > > === Got errors: === > 14:16: Compiler crash in AnalyseDeclarationsTransform > > ERROR > > == > ERROR: runTest (__main__.CythonRunTestCase) > compiling (cpp) and running fused_cpp > -- > Traceback (most recent call last): > File "runtests.py", line 993, in run > ext_so_path = self.runCompileTest() > File "runtests.py", line 705, in runCompileTest > self.test_directory, self.expect_errors, self.annotate) > File "runtests.py", line 928, in compile > self.assertEquals(None, unexpected_error) > AssertionError: None != u'14:16: Compiler crash in > AnalyseDeclarationsTransform' > > -- > Ran 1 test in 0.350s > > FAILED (errors=1) > ALL DONE > > > ___ > cython-devel mailing list > cython-devel@python.org > https://mail.python.org/mailman/listinfo/cython-devel ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Cython alpha 0.24
Hi, I just built a large project with the alpha version. All looks good. The only new/odd thing is a lot of warnings of this flavor: warning: View.MemoryView:219:4: 'property memview:' syntax is deprecated, use '@property' warning: View.MemoryView:536:4: 'property T:' syntax is deprecated, use '@property' warning: View.MemoryView:543:4: 'property base:' syntax is deprecated, use '@property' warning: View.MemoryView:548:4: 'property shape:' syntax is deprecated, use '@property' warning: View.MemoryView:553:4: 'property strides:' syntax is deprecated, use '@property' warning: View.MemoryView:562:4: 'property suboffsets:' syntax is deprecated, use '@property' warning: View.MemoryView:570:4: 'property ndim:' syntax is deprecated, use '@property' warning: View.MemoryView:575:4: 'property itemsize:' syntax is deprecated, use '@property' warning: View.MemoryView:580:4: 'property nbytes:' syntax is deprecated, use '@property' warning: View.MemoryView:585:4: 'property size:' syntax is deprecated, use '@property' warning: View.MemoryView:984:4: 'property base:' syntax is deprecated, use '@property' warning: View.MemoryView:219:4: 'property memview:' syntax is deprecated, use '@property' warning: View.MemoryView:536:4: 'property T:' syntax is deprecated, use '@property' warning: View.MemoryView:543:4: 'property base:' syntax is deprecated, use '@property' warning: View.MemoryView:548:4: 'property shape:' syntax is deprecated, use '@property' warning: View.MemoryView:553:4: 'property strides:' syntax is deprecated, use '@property' warning: View.MemoryView:562:4: 'property suboffsets:' syntax is deprecated, use '@property' warning: View.MemoryView:570:4: 'property ndim:' syntax is deprecated, use '@property' warning: View.MemoryView:575:4: 'property itemsize:' syntax is deprecated, use '@property' warning: View.MemoryView:580:4: 'property nbytes:' syntax is deprecated, use '@property' --Kevin On Fri, Mar 11, 2016 at 12:26 AM Robert Bradshaw wrote: > We are getting ready to push a new major release. A first alpha is up > at http://cython.org/release/Cython-0.24a0.tar.gz > > To avoid surprises, please test and report. > > Thanks, > Robert > ___ > cython-devel mailing list > cython-devel@python.org > https://mail.python.org/mailman/listinfo/cython-devel > ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
