Hello everybody, > If some minor things come up, there likely will be a 0.1.1 at the end of > August. After that I am moving to a new house and you know how time > consuming that can be.
There is now a 0.1.1 release, which has some quirks fixed that showed up in 0.1, and some more work inside. Esp. the handling of exceptions and assertions has seen much improvement towards compatability. Now it has sys.exc_info() working as expected, so modules like traceback, do the correct thing too. I also merged the CPython tests as far as possible, and added support for a few smaller things too. The diff now seems almost exclusively caused by unicode repr troubles (I saw that Cython users encounter these too), having no function.func_code and otherwise very small things. Managing all these tests appears to be a very good test coverage. http://kayhayen24x7.homelinux.org/blog/2010/08/nuitka-minor-update/ I have started though to migrate it from "compiler" module which was the only thing available and usable at the time I started in the 2.5 time frame, to the "ast" module, which seems good starting 2.6. Once this is completed, likely this week, it's not a huge thing, the differences to "compiler" appear to be mostly improvements, then I will have a 0.2 with which I will do some serious benchmarking. Can you point me to existing benchmarks for Cython vs. CPython comparisons? I would like to start from there and extend what you have to this. But looking at http://hg.cython.org/cython-devel/file/979c14fc453e/tests didn't immediately put anything into my face. I noticed recently that Cython has had a performance regression (was it in Sage) that went unnoticed. So does that mean, you don't have run time speed performance regression tests? I currently only have "pystone" as a benchmark, which is a bit difficult to look at, because it's not good at telling you why it has that speed, aggregating everything into one. If you don't have anything, I will glady contribute something to call the performance regression tester. Ever since I starting to optimize with Valgrind, I wondered if it wouldn't be perfectly well suited to the task of noting a change in the total number of cycles to run test programs. What do you think? Yours, Kay Hayen _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
