Hi all, So here's a second go at Cython 0.13 beta. I'm posting it to the usual place, namely:
http://www.cython.org/release/Cython-0.13.beta1.tar.gz This definitely still isn't ready to go out the door, hence the "beta" instead of "rc." A few notes: * We've been running into an interesting problem with rare (~0.05% of the time) segfaults on Sage startup. Interestingly, this has apparently been around a while -- Robert and I have run a handful of tests, and this behavior was already there with Cython-0.12.1. (We didn't try to bisect at all, we just wanted to confirm that it wasn't completely new.) Our not-completely-scientific analysis suggests that the rate of segfaults hasn't changed since the last Cython release, so our current plan is to get this release (finally!) out the door, and then start trying to diagnose this further. There are some questions about whether or not this might be hardware-related, but given how rare the failures are, I don't think we've really run the tests anywhere enough to say we're *not* seeing the same problem elsewhere. * Since it seems like every third email to cython-users has confusion about bool being a C++ vs. Python type as its root cause, Robert's gone ahead and made bool an invalid type identifier. (This is already pushed, so this might not be news.) The plan is to simply make the types explicit for now (which Robert has already done, see cimport cpython.bool and libcpp.bool) and decide later whether or not bool should be a valid identifier by itself. I'm going to add a FAQ entry about this, but I'm going to do it when I'm more coherent (because writing FAQ entries takes more concentration than cutting a beta?). Things we need to fix before release: * There are a handful of unicode-related doctest failures that Lisandro ran into in another thread. I'm guessing Stefan will know what's going on here faster than anyone else? ;) * We need to clean up the last of the fallout from #561 -- if I'm reading the corresponding thread correctly, Carl's got a fix for that we need to push. If so, Carl, feel free to push that. (My machine is currently rebuilding Sage, so I can't test this myself.) Is there anything else that anyone can think of that's blocking us on 0.13? If not, my plan is to cut an rc as soon as we get all the above failures passing, and plan on releasing a few days after that. If anyone has any other thoughts, now's the time. -cc _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
