docs for hotshot module

[anthonybaxter]

BPO	698505
Nosy	@freddrake, @rhettinger
Files	libhotshot.tex: libhotshot.tex lib.tex.patch: patch to lib.tex

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2003-04-07.12:38:24.000>
created_at = <Date 2003-03-06.05:36:31.000>
labels = ['docs']
title = 'docs for hotshot module'
updated_at = <Date 2003-04-07.12:38:24.000>
user = 'https://bugs.python.org/anthonybaxter'

bugs.python.org fields:

activity = <Date 2003-04-07.12:38:24.000>
actor = 'anthonybaxter'
assignee = 'anthonybaxter'
closed = True
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2003-03-06.05:36:31.000>
creator = 'anthonybaxter'
dependencies = []
files = ['5071', '5072']
hgrepos = []
issue_num = 698505
keywords = ['patch']
message_count = 5.0
messages = ['42961', '42962', '42963', '42964', '42965']
nosy_count = 3.0
nosy_names = ['fdrake', 'anthonybaxter', 'rhettinger']
pr_nums = []
priority = 'normal'
resolution = 'accepted'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue698505'
versions = []

[anthonybaxter]

The attached provides documentation for the hotshot
module. Assigning to Fred for review.

[anthonybaxter]

Logged In: YES
user_id=29957

stupid sourceforge tracker.

[rhettinger]

Logged In: YES
user_id=80475

The TeX markup checks out fine.

Consider documenting lineevents and linetimings which
are exposed upon: import hotshot.

For the example, consider adding a comment line at
the beginning with hints that the example produces large
files and takes a long time to run.

[freddrake]

Logged In: YES
user_id=3066

Please commit. Further changes can be made in CVS.

Thanks!

[anthonybaxter]

Logged In: YES
user_id=29957

checked in. I'll look into adding further docs as I get more
into the code I'm
writing to sit on top of hotshot (to replace pstats)...