Stefan Behnel, 08.05.2013 20:43: > in the past, Robert and I have invested some work into supporting profiling > and tracing in Cython, and I would like to see this finalised. While Python > level tracing and profiling might not seem like the ideal tools for > performance critical Cython code, they are actually pretty handy when much > of your code is Python code and you want to do, say, coverage analysis over > your whole code base, without having to exclude the Cython parts. > > So I've opened a ticket that highlights the missing bits. > > http://trac.cython.org/cython_trac/ticket/815 > > If anyone's interested in pursuing this, I'd be glad to help getting you on > the right track. I don't even think there's all that much left to do, but > it's still a bit of cleanup and maybe some naughty little details along the > way. Would make a good entry project, IMHO.
And maybe I should mention that there's a second side to this: with another bit of work to improve the configuration of code objects, Cython implemented Python functions could become even more Python compatible by allowing for better introspection, e.g. of function signatures and their parameters. A PEP 362 implementation (the __signature__ API) doesn't seem all that far either. http://www.python.org/dev/peps/pep-0362/ > Anyone interested? Stefan _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
