Robert Bradshaw wrote: > As mentioned earlier, it's about time to release Cython 0.12.
Totally. > What I see that needs to happen is > > 1) Get Sage working with the new Cython. I've gotten Sage to compile > and nearly all doctests passing You can switch the cascaded assignment work-around back to the original code, I fixed #409. > I think I'm down to one bug, > somewhere in exception handling, but I haven't been able to look at it > much yet Any more hints on this? I might be able to help out. > I'd assume lxml and other developer projects are building > with the current head. lxml tests fine, but it's certainly worth removing some C-isms from its code once I start depending Cython 0.12. If all those new optimisations had been in Cython two years ago, the code would look a lot cleaner today. > 2) We should go onto the trac server (link below) and either resolve/ > bump any tickets that are not going happen in the next week or two. I'll see that I get the tickets closed that I'm still working on. Most of the currently tickets do not look like the need fixing right now, but we should at least get all tests working on the supported platforms. > 3) Widespread testing. Oh, yes, please! :) It seems from the reports we had on the list that many users have already been running cython-devel recently. But it would be good to get some feedback especially from Windows/Mac users, as I expect most developers to be on Linux nowadays. > Shortly we should put out an alpha and some > release candidates. It would probably be good to have a feature freeze > and push bug fixes only (for this branch). +1 > There's a lot of new stuff > in this release (all of -unstable) so I'd like to pound it hard, > including Windows building and projects that don't normally compile > with the -devel branch. Given the amount of changes, I'd also expect at least two release candidates, and I really hope that people will exercise them. It's definitely worth switching from 0.11. Remember: *before* a new major release is the best time to get your bugs fixed, not afterwards. > Lets aim for a serious alpha, or hopefully even a release candidate, > by the end of the month. Sounds like a plan. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
