Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment:
> So I'm open to ideas and am willing to submit improved patches for 3.2 I offered some ideas in my last message. In addition, I would like to see profile and trace documentation to converge to similar structure and use similar terminology. In particular, I don't like "Run *cmd* under control of the Trace object" because Trace is not a debugger and does not "control" the execution. I think the explanation at http://docs.python.org/dev/py3k/library/profile.html#cProfile.run is better. On the other hand, I like "Programming Interface" as the title of the API section better than "Reference Manual" in profile docs. I hope we can change both trace and profile sections and retain the best choices. ---------- priority: high -> normal _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9264> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
