On Nov 15, 2004, at 5:44 AM, Nick Coghlan wrote: > Ah, OK, I think I better understand what you're trying to achieve now. > Does knowing that the 2.4 profiler splits out C invocations from the > calling Python methods make a difference here? > > The 2.4 profiler is the only one I've made heavy use of - I'd forgotten > that the 2.3 profiler didn't split out the C functions. > > I've also discovered that the profiler documentation in Python 2.4 > still > describes the old behaviour (i.e. C-code time getting charged to the > calling Python function). (I'll put a bug report on SF for that one) Doh, I thought I'd found all of the places in the doc that needed to be corrected. If you file an SF bug, or just let me know where, I'll fix the documentation to reflect the current state of things. -- Nick
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4