Hi all, So I hope you're sitting down for this one: I just ran a complete build and test of Sage with a recent cython-devel + some extra patches, and everything builds and passes. Huzzah! I just need to add some tests to my patches tomorrow and I'll push those, along with posting a few patches to the Sage library. (Robert, you're going to have a few easy reviews coming up! :P)
Here's my current plan: - Saturday: add tests, push some patches. (I'm flying to CA tomorrow, which is a perfect time for this.) - Sunday: cut cython-0.13.alpha0, *finally*. After that, I'm going to pull the new patches into cython-closures, and test Sage with that. Here are some famous last words: I don't expect to run into too much trouble, because nothing is *using* the new features. If that goes well, I'll cut alpha1 shortly thereafter. (There's some other code here and there, but at least I'm familiar with parts of it already.) If not, we'll see how bad the fallout is and make a decision. My goal is to get alpha1 out and give people, say, a week or so to try it out, see what trouble they run into, and then plan on doing an actual release shortly thereafter. Thoughts? Comments? What's the schedule usually like? For the curious: there was nothing terribly bad about this particular release -- most of the holdup was due to other things (like buying a house, moving, designing a new course this past quarter, baby illnesses, that kind of stuff). There was one significant change from 0.12.1, though -- "safe" type inference is turned on by default. As you might expect, this causes *lots* of small changes, especially in a codebase like Sage. So there were a bunch of bugs to track down -- most of which weren't good for hunting 30 minutes at a time. ;) -cc _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
