svn+ssh://pythondev@svn.python.org/python/branches/release27-maint

........
  r83354 | georg.brandl | 2010-07-31 21:07:37 +0200 (Sa, 31 Jul 2010) | 1 line

  #9328: string format methods return strings.
........
  r83365 | georg.brandl | 2010-07-31 23:22:36 +0200 (Sa, 31 Jul 2010) | 1 line

  #1019882: if start() and stop() were not in the same stack frame, stats.load() would crash with IndexError.
........

#1019882: if start() and stop() were not in the same stack frame, stats.load() would crash with IndexError.

There's one major and one minor category still unfixed:
doctests are the major category (and I hope to be able to augment the
refactoring tool to refactor bona fide doctests soon);
other code generating print statements in strings is the minor category.

(Oh, and I don't know if the compiler package works.)

(a) "except E, V" -> "except E as V"
(b) V is now limited to a simple name (local variable)
(c) V is now deleted at the end of the except block

Weinberg).  This changes all uses of deprecated tempfile functions to
the recommended ones.

and should never return None.  (It only did this for an old version of
HotShot that was trying to still work with a patched Python 2.1.)

Remove the crufty support for Python's that don't have StopIteration;
the HotShot patch for Python 2.1 has not been maintained.

file object that LogReader opens.  Used it then in test_hotshot; the
test passes again on Windows.  Thank Guido for the analysis.

codebase, so get rid of the pre-2.2 contingency.

- Add comment explaining the structure of the stack.
- Minor optimization: make stack tuple directly usable as part of return
  value for enter/exit events.

Avoid adding Python wrappers around the underlying C profiler if possible;
the extra layer of calls can lead to confusion in interpreting the logs.

dictionary instead of building a new one, and provide an overridable method
to allow subclasses to catch ADD_INFO records that are not part of the
initial block of ADD_INFO records created by the profiler itself.

hotshot.stats.load(logfilename) returns a pstats.Stats instance, which is
about as compatible as it gets.

    changing an application to collect profile data on one part of the
    app while still making use of the profiled component, without relying
    on side effects.

Add support for extracting function names from the log file, keeping the
extract-names-from-sources support as a fallback.

tool; look for that on Monday.