>> IMO cython-closures should be our new cython-unstable, to make sure it >> is tested and merged and keep the number of (cooperative) branches down. > > I don't mind either way. I agree that cython-closures can really use some > more testing and shouldn't delay 0.12. >
I actually just posted a patch (actually, two patches, because I forgot to run tests before I pushed) to that branch. This is the bug that Robert ran into during our SD15 talk ... it should work now. I'm going to try and run a bunch more tests tonight, but I'm also +1 on cython-closures becoming the new cython-unstable. -cc _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
