I'd like to take this opportunity to thank the people involved in tracking down this nasty Cython bug and preparing #715 and related tickets in the first place. This is mainly the work of Simon King, Jean-Pierre Flori and Nils Bruin. They probably managed one of the most difficult patches recently put in Sage, because changing caching has so many consequences all over Sage. Thanks for the good work!
On 2013-01-14 21:12, Nils Bruin wrote: > With 5.6 almost out the door, it is perhaps time to prepare some > infrastructure maintenance tickets in line for inclusion in 5.7. In > particular, these tickets spring to mind: > > http://trac.sagemath.org/sage_trac/ticket/12215 > http://trac.sagemath.org/sage_trac/ticket/12313 > http://trac.sagemath.org/sage_trac/ticket/13370 > http://trac.sagemath.org/sage_trac/ticket/13378 > > Most of these tickets look like they were in pretty good shape the > last time they were touched, but they probably need to be rebased and/ > or updated/reviewed. > > I'd like to highlight that the last bug that was caught as a result of > this kind of work turned out to be a bug in cython, affecting all > classes. The bug got triggered if a GC happened during the > deallocation of a cython class. This can happen in a lot of cases; > just by coincidence did this get triggered by one of our doctests in > conjunction with the merger of #715. However, there were probably > plenty of unexplained sage crashes out there that were really due to > this problem. Merging these tickets really does make sage more healthy! -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
