Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Issue #14428: Use the new time.perf_counter() and time.process_time() functions | Victor Stinner | 2012-04-29 | 1 | -2/+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. | ||||
* | Fix most trivially-findable print statements. | Guido van Rossum | 2007-02-09 | 1 | -2/+2 |
| | | | | | | | | | 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.) | ||||
* | SF patch #701494: more apply removals | Raymond Hettinger | 2003-04-06 | 1 | -1/+1 |
| | |||||
* | Measure performance of sub(), split(), findall(). | Guido van Rossum | 1998-07-17 | 1 | -0/+23 |