I'm writing a system where I build data structures for searching using a blend of Cython and Python code. Ideally, though, the search operations (performed after the structures have been built) should be initiated from Python, but then stay in as pure C as possible (to keep the Python/Cython overhead to an absolute minimum).
Now, I could (and probably will) inspect the code to determine this "manually", but I was thinking -- perhaps I can automate it somehow? At least partially? And I thought I'd ask if you might have any ideas in that respect. In other words, I'd like to profile the code, to see where it goes through Cython/the Python C API (or even Python code), so I can eliminate those calls. Could I just use a standard profiler here, perhaps? (I'm guessing all C stuff will then just be black-box references, but that's OK, I guess.) Any other ideas? Some global location where I could insert a counter into the generated code? Some existing Cython magic? - M -- Magnus Lie Hetland http://hetland.org _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
