Re: [Cython] 0.16 release
mark florisson, 30.03.2012 19:24: > The release build looks good now, I'm thinking of pushing a second and > final beta out there tomorrow. If anyone wants to get something in, > now is the time to raise voice. Note that Dag's NumPy specialisation broke the Sage build by introducing a compiler crash. https://sage.math.washington.edu:8091/hudson/view/cython-devel/job/sage-build/1064/consoleFull The problem is that the new code is already triggered during type inference (i.e. before type analysis) and then crashes the compiler because it accesses types that are not known yet. Stefan ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] 0.16 release
On 31 March 2012 10:14, Stefan Behnel wrote: > mark florisson, 30.03.2012 19:24: >> The release build looks good now, I'm thinking of pushing a second and >> final beta out there tomorrow. If anyone wants to get something in, >> now is the time to raise voice. > > Note that Dag's NumPy specialisation broke the Sage build by introducing a > compiler crash. > > https://sage.math.washington.edu:8091/hudson/view/cython-devel/job/sage-build/1064/consoleFull > > The problem is that the new code is already triggered during type inference > (i.e. before type analysis) and then crashes the compiler because it > accesses types that are not known yet. > > Stefan > ___ > cython-devel mailing list > cython-devel@python.org > http://mail.python.org/mailman/listinfo/cython-devel Thanks for pointing that out Stefan. It would probably work if it passed in 'obj_type' to the numpy_transform_attribute_node, and used that instead of node.type. Alternatively, it could just wait until the type is set through analyse_expressions. ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] 0.16 release
mark florisson, 31.03.2012 11:31: > On 31 March 2012 10:14, Stefan Behnel wrote: >> mark florisson, 30.03.2012 19:24: >>> The release build looks good now, I'm thinking of pushing a second and >>> final beta out there tomorrow. If anyone wants to get something in, >>> now is the time to raise voice. >> >> Note that Dag's NumPy specialisation broke the Sage build by introducing a >> compiler crash. >> >> https://sage.math.washington.edu:8091/hudson/view/cython-devel/job/sage-build/1064/consoleFull >> >> The problem is that the new code is already triggered during type inference >> (i.e. before type analysis) and then crashes the compiler because it >> accesses types that are not known yet. > > Thanks for pointing that out Stefan. It would probably work if it > passed in 'obj_type' to the numpy_transform_attribute_node, and used > that instead of node.type. Alternatively, it could just wait until the > type is set through analyse_expressions. Thanks for fixing them. The release branch seems to be in good shape for a final beta release now. On a related note, the current master looks more like a 0.17 to me than a 0.16.1 when I compare it to the current release branch. We could just wait for a couple of weeks to collect bugs in 0.16 from user reports (and features as they come in), and then push out a 0.17. I hope the pending PyPy changes will also be ready enough for a release by then, that would round up the feature list quite nicely. Stefan ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] 0.16 release
On 31 March 2012 17:15, Stefan Behnel wrote: > mark florisson, 31.03.2012 11:31: >> On 31 March 2012 10:14, Stefan Behnel wrote: >>> mark florisson, 30.03.2012 19:24: The release build looks good now, I'm thinking of pushing a second and final beta out there tomorrow. If anyone wants to get something in, now is the time to raise voice. >>> >>> Note that Dag's NumPy specialisation broke the Sage build by introducing a >>> compiler crash. >>> >>> https://sage.math.washington.edu:8091/hudson/view/cython-devel/job/sage-build/1064/consoleFull >>> >>> The problem is that the new code is already triggered during type inference >>> (i.e. before type analysis) and then crashes the compiler because it >>> accesses types that are not known yet. >> >> Thanks for pointing that out Stefan. It would probably work if it >> passed in 'obj_type' to the numpy_transform_attribute_node, and used >> that instead of node.type. Alternatively, it could just wait until the >> type is set through analyse_expressions. > > Thanks for fixing them. The release branch seems to be in good shape for a > final beta release now. > > On a related note, the current master looks more like a 0.17 to me than a > 0.16.1 when I compare it to the current release branch. We could just wait > for a couple of weeks to collect bugs in 0.16 from user reports (and > features as they come in), and then push out a 0.17. I hope the pending > PyPy changes will also be ready enough for a release by then, that would > round up the feature list quite nicely. Indeed, I was getting ready for a release, but I almost forgot to merge over some fixes from the _fused_dispatch branch (to correctly specialize np.ndarray and C++ templates). So I'm doing that now, which also exposed a deepcopy python 2.4 bug. I'm planning an RC for tonight. > Stefan > ___ > cython-devel mailing list > cython-devel@python.org > http://mail.python.org/mailman/listinfo/cython-devel ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
[Cython] Cython 0.16 Release Candidate
We are happy to announce the first release candidate for Cython 0.16, you can grab it from here: http://wiki.cython.org/ReleaseNotes-0.16 Since the beta last month several issues have been fixed, including the NumPy array attribute access deprecation, which are now rewritten to use the NumPy macros. Another serious bug in the reversed(range()) optimization was disabled, a C compiler bug on OS X Lion in OpenMP code was circumvented, the documentation for fused types has been improved, some bugs related to fused C++ and buffers types have been fixed, and nogil was added to the included STL declarations. I encourage everyone to give it a try, see if your project still compiles and works, and if it doesn't to take up those torches and pitchforks from your desks, you know where to find us. Enjoy! ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
