Robert Bradshaw wrote: > As mentioned earlier, it's about time to release Cython 0.12. 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 (I think I'm down to one bug, > somewhere in exception handling, but I haven't been able to look at it > much yet). I'd assume lxml and other developer projects are building > with the current head. > > 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. > Also, if there are any other blockers that need to be put in this > list, please do so. To all: if there's something you're really like to > see get into the next release, please speak up now. (No promises, but > at the very least it'll help assign priorities.) > > 3) Widespread testing. 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). 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. > Also, let's get as many as possible to test with the refnanny turned on (and let's make it easy, say, let's include the code to stick in ones setup.py in the RC release notes).
Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
