Craig Citro, 02.02.2010 01:27: > So this has already been discussed in several other threads, but I > think the current plan is: once Robert releases 0.12.1, we'll pull all > the changes from there into the cython-closures branch, and turn > cython-closures into cython-devel for 0.13. I was chatting with > Robert, and I think I'm happy to be the release manager for 0.13, > unless there are any objections ...
Meaning, he talked you into it and you naively agreed? ;) > - I just finished (taking forever to) add a big battery of tests in > the cython-closures branch. Way cool. Thanks! The tests look absolutely machine generated, BTW. :) > I ended up adding a wee bit of code, and > then working out a few reference counting bugs that we hit with > closures. I've committed all the tests into the closures branch (as a > series of 5 files; gcc and g++ were choking with everything in one > file). I actually tried to use tcc for running the test suite a while ago, but it crashed for me. Usually, dactivating most optimisations with "gcc -O1" speeds up the test runs by quite a bit, and might also drop the memory requirement a little. > - In the process of doing this, the refnanny complained a few times > -- so I wrote myself some notes on how reference counting should be > working. I realized these might be useful in general, so I've added a > little extra text and posted it on the wiki: > > http://wiki.cython.org/refcounting The Wiki appears to be dead right now. > - There is one place where I really didn't test out the closures code > much, especially with an eye towards memory leaks/reference counting > troubles, and that's error handling. Ah, right, that's a long standing deficiency of the test suite anyway. I bet a coverage report would reveal that 99% of the error handling code is never exercised, really. Much is that is because there are tons of dead code that are only ever taken on memory errors (or other Python internal errors that can't really be produced in a test suite), but at least a tiny bit is simply never tested. Are there any special error cases in the closures code that would deserve special testing? > I think the next step is to start working on the > generators implementation that came up in some other threads, and is > outlined on the wiki. I'm planning on starting on that soon, if no one > beats me to it Cool. How much time can you spare on this? If you need any help, please ask (and make sure you're not 80% through with it before you ask ;). Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
