Nick Bastin writes:
> Does anybody know the current state of hotshot? I read on some of the
> twisted mailing lists a while back that someone tried it but had some
> problems (can't remember what off the top of my head...have to search
> the archives), and was wondering if it was regarded as complete (and if
> there was any documentation that talks about how the code coverage
> aspect is supposed to be used).
HotShot has had some attention, and has been found useful, but I don't
think of it as really finished. Issues have been reported relating to
making measurements when threads are involved, but I've not had any
time available for it.
There is some documentation in the Library Reference:
http://www.python.org/doc/current/lib/module-hotshot.html
What's in the standard library contains the low-level profiler and a
hotshot.stats module that allows the same kind of analysis and
reporting as the pstats module supports for the older profile module.
There is support for collecting the information needed to measure
coverage, but no higher-level tools to make it easy to use. That's
the case for the per-line performance measurements as well.
Any improvements to the analysis and reporting tools, or
documentation, would be quite welcome!
-Fred
--
Fred L. Drake, Jr. <fdrake at acm.org>
PythonLabs at Zope Corporation
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