Hi all, I think the subject line pretty much says it all -- I just successfully built sage-4.4.4 against the tip of cython-closures, and it builds, runs, and passes all doctests(*). As far as I'm concerned, that means it's time to roll ourselves an alpha. (Robert, do you want to tell me what steps are involved in that? Is there a list somewhere?) Also, what's the general rule for avoiding someone clobbering the "working" state with a push? Should I just add a tag for "0.13-alpha0" and we could always recover from there?
I just ran the Cython tests in the closures branch itself -- it looks like there are a few doctest failures with the recent code there. I'm happy to start helping with these tomorrow, but can we designate cython-closures as "bugfix only" until the actual release? For that matter, with closures becoming devel, soon we won't need a closures branch anymore ... finally. ;) (*) Actually, there's one doctest failure going on -- but it's a bug in Sage, which I've reported. (http://trac.sagemath.org/sage_trac/ticket/9524) It could be that there's an associated underlying Cython bug, but I don't think so in this case -- either way, it shouldn't stop us from rolling an alpha, and a release if we still think it's not an underlying Cython bug. -cc _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
