summaryrefslogtreecommitdiffstats
path: root/Lib/profile.py
Commit message (Collapse)AuthorAgeFilesLines
* Issue #14428: Use the new time.perf_counter() and time.process_time() functionsVictor Stinner2012-04-291-34/+2
| | | | | | | | | | | | * Replace "time.clock on windows, or time.time" with time.perf_counter() * profile module: only use time.process_time() instead of trying different functions providing the process time * timeit module: use time.perf_counter() by default, time.time() and time.clock() can still be used using --time and --clock options * pybench program: use time.perf_counter() by default, add support for the new time.process_time() and time.perf_counter() functions, but stay backward compatible. Use also time.get_clock_info() to display information of the timer.
* strip trailing wsBenjamin Peterson2011-06-271-3/+3
|
* update profile license (closes #12417)Benjamin Peterson2011-06-271-24/+15
|
* #9428: fix running scripts from profile/cProfile with their own name and the ↵Georg Brandl2010-08-021-10/+18
| | | | right namespace. Same fix as for trace.py in #1690103.
* Remove traces of MacOS9 support.Ronald Oussoren2010-05-051-9/+0
| | | | Fix for issue #7908
* Issue #4282: Fix the main function of the profile module for a non-ASCIIVictor Stinner2010-03-221-4/+1
| | | | | script, open the file in binary mode and not in text mode with the default (utf8) encoding.
* convert shebang lines: python -> python3Benjamin Peterson2010-03-111-1/+1
|
* Merged revisions 74773 via svnmerge fromMatthias Klose2009-09-131-2/+2
| | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/trunk ........ r74773 | matthias.klose | 2009-09-13 17:09:24 +0200 (So, 13 Sep 2009) | 2 lines Issue #6635: Fix profiler printing usage message. ........
* Remove the just-removed "help" from __all__.Georg Brandl2009-09-041-1/+1
|
* Remove backwards compatibility stuff from profile/cProfile.Georg Brandl2009-09-041-7/+0
|
* Kill execfile(), use exec() insteadNeal Norwitz2007-08-121-1/+6
|
* - PEP 3106: dict.iterkeys(), .iteritems(), .itervalues() are now gone;Guido van Rossum2007-02-111-2/+2
| | | | | | | | | | and .keys(), .items(), .values() return dict views. The dict views aren't fully functional yet; in particular, they can't be compared to sets yet. but they are useful as "iterator wells". There are still 27 failing unit tests; I expect that many of these have fairly trivial fixes, but there are so many, I could use help.
* Fix most trivially-findable print statements.Guido van Rossum2007-02-091-8/+8
| | | | | | | | | 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.)
* Patch #1550800: make exec a function.Georg Brandl2006-09-061-1/+1
|
* Get rid of dict.has_key(). Boy this has a lot of repercussions!Guido van Rossum2006-08-181-1/+1
| | | | | | Not all code has been fixed yet; this is just a checkpoint... The C API still has PyDict_HasKey() and _HasKeyString(); not sure if I want to change those just yet.
* test and fix for buggy handling of exceptions raised by C functions,Armin Rigo2005-09-201-1/+1
| | | | | causing the profiler to crash on an AssertionError if the same Python function catches multiple exceptions from C functions.
* Patch #645894: Use getrusage for computing the time consumption inMartin v. Löwis2005-03-031-2/+20
| | | | profile.py if available.
* Whitespace normalization.Tim Peters2005-01-101-3/+3
|
* Bug #489256: remove out of date and out of place profile.doc, and letJohannes Gijsbers2005-01-101-13/+3
| | | | profile.help() point at the library reference instead of profile.doc.
* Move code in __name__ == '__main__' block into main() function, rewrite code soJohannes Gijsbers2005-01-091-16/+14
| | | | there's no need to subclass OptionParser.
* Using repr() generates entries that the current stats package can'tNicholas Bastin2004-07-121-4/+4
| | | | collate, so setting it back to the function name
* Fix SF Bug #989066Nicholas Bastin2004-07-121-4/+4
|
* Whitespace normalization.Tim Peters2004-07-071-2/+2
|
* Enable the profiling of C functions (builtins and extensions)Nicholas Bastin2004-03-241-1/+30
|
* Add runctx to __all__.Guido van Rossum2004-03-231-1/+1
|
* Added command line options for profile.py - one for stats output fileNicholas Bastin2004-03-231-13/+27
| | | | and one for sort order when using stdout. Uses optparse.
* Added global runctx function to profile to fix SF Bug #716587Nicholas Bastin2004-03-221-0/+17
|
* Replace backticks with repr() or "%r"Walter Dörwald2004-02-121-2/+2
| | | | From SF patch #852334.
* Remove unneeded import.Guido van Rossum2003-10-221-1/+0
|
* Replace a reduce() with sum().Raymond Hettinger2003-10-221-3/+2
|
* Get rid of many apply() calls.Guido van Rossum2003-02-271-1/+1
|
* Replaced .keys() with dictionary iteratorsRaymond Hettinger2002-06-021-4/+3
|
* Replace boolean test with is None.Raymond Hettinger2002-06-011-1/+1
|
* SF 563203. Replaced 'has_key()' with 'in'.Raymond Hettinger2002-06-011-2/+2
|
* Added a missing period at the end of an error message.Fred Drake2001-12-051-2/+2
|
* Minor code cleanups based on comments from Neal Norwitz.Fred Drake2001-10-171-3/+2
|
* Repair key stutter + auto-complete ugliness.Tim Peters2001-10-091-2/+2
|
* Allow the profiler's calibration constant to be specified in the constructorTim Peters2001-10-091-19/+27
| | | | | | | | call, or via setting an instance or class vrbl. Rewrote the calibration docs. Modern boxes are so friggin' fast, and a profiler event does so much work anyway, that the cost of looking up an instance vrbl (the bias constant) per profile event just isn't a big deal.
* A brand new implementation of Profile.calibrate(). This measures anTim Peters2001-10-091-41/+62
| | | | | | | | | actual run of the profiler, instead of timing a simplified simulation of part of what the profiler does. It computes a constant about 60% higher on my Win98SE box than the old method, and the new constant appears much more realistic. Deleted the undocumented simple(), instrumented(), and profiler_simulation() methods (which existed only to support the previous calibration method).
* Typo repair in comment.Tim Peters2001-10-071-1/+1
|
* Guido points out that the comments for self.cur[2] were subtly butTim Peters2001-10-071-17/+29
| | | | | | | | seriously wrong. This started out by just fixing the docs, but then it occurred to me that the doc confusion propagated into misleading vrbl names too, so I also renamed those to match reality. As a result, INO the time computations are much easier to understand now (within the limitations of vast quantities of 3-character names <wink>).
* At Guido's request, changed the code that's conceptually asserting stuffTim Peters2001-10-071-11/+9
| | | | to use assert stmts (was raising unexpected kinds of exceptions).
* Repair some longstanding comment errors:Tim Peters2001-10-071-4/+4
| | | | | | + The last index in the timing tuple is 4, not 5 (noted by Guido). + The poorly named trace_dispatch_i works with float return values too.
* Remove code and docs for the OldProfile and HotProfile classes: codeTim Peters2001-10-071-115/+0
| | | | | hasn't worked in years, docs were wrong, and they aren't interesting anymore regardless.
* The fix to profile semantics broke the miserable but advertised way toTim Peters2001-10-051-25/+26
| | | | | derive Profile subclasses. This patch repairs that, restoring negative tuple indices. Yuck? You bet.
* Hopefully fix the profiler right. Add a test suite that checks thatGuido van Rossum2001-10-041-18/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | it deals correctly with some anomalous cases; according to this test suite I've fixed it right. The anomalous cases had to do with 'exception' events: these aren't generated when they would be most helpful, and the profiler has to work hard to recover the right information. The problems occur when C code (such as hasattr(), which is used as the example here) calls back into Python code and clears an exception raised by that Python code. Consider this example: def foo(): hasattr(obj, "bar") Where obj is an instance from a class like this: class C: def __getattr__(self, name): raise AttributeError The profiler sees the following sequence of events: call (foo) call (__getattr__) exception (in __getattr__) return (from foo) Previously, the profiler would assume the return event returned from __getattr__. An if statement checking for this condition and raising an exception was commented out... This version does the right thing.
* Undo previous patch; it did not quite work out.Fred Drake2001-10-031-1/+1
|
* Change the sense of a test in how the profiler interprets exception events.Fred Drake2001-09-271-1/+1
| | | | | This should fix a bug in how time is allocated during exception propogation (esp. in the presence of finally clauses).
* Fix two bugs detected by PyChecker: there's no need for redundantGuido van Rossum2001-08-091-1/+1
| | | | "import MacOS", and there *is* a need for "import operator".
* An import MacOS was missing after the code-rearranging. Added.Jack Jansen2001-06-191-0/+1
|
generated by cgit v0.12 at 2024-11-18 06:46:32 (GMT)