[EDIT] FILE: timeit.pyo
� z fc @ s d Z d d l Z d d l Z d d l Z y d d l Z Wn e k rS d Z n Xd g Z d Z d Z d Z e j d k r� e j Z n e j Z d Z d � Z d � Z d d d � � YZ d d e e d � Z d d e e e d � Z d d d � Z e d k re j e � � n d S( s� Tool for measuring execution time of small code snippets. This module avoids a number of common traps for measuring execution times. See also Tim Peters' introduction to the Algorithms chapter in the Python Cookbook, published by O'Reilly. Library usage: see the Timer class. Command line usage: python timeit.py [-n N] [-r N] [-s S] [-t] [-c] [-h] [--] [statement] Options: -n/--number N: how many times to execute 'statement' (default: see below) -r/--repeat N: how many times to repeat the timer (default 3) -s/--setup S: statement to be executed once initially (default 'pass') -t/--time: use time.time() (default on Unix) -c/--clock: use time.clock() (default on Windows) -v/--verbose: print raw timing results; repeat for more digits precision -h/--help: print this usage message and exit --: separate options from statement, use when statement starts with - statement: statement to be timed (default 'pass') A multi-line statement may be given by specifying each line as a separate argument; indented lines are possible by enclosing an argument in quotes and using leading spaces. Multiple -s options are treated similarly. If -n is not given, a suitable number of loops is calculated by trying successive powers of 10 until the total time is at least 0.2 seconds. The difference in default timer function is because on Windows, clock() has microsecond granularity but time()'s granularity is 1/60th of a second; on Unix, clock() has 1/100th of a second granularity and time() is much more precise. On either platform, the default timer functions measure wall clock time, not the CPU time. This means that other processes running on the same computer may interfere with the timing. The best thing to do when accurate timing is necessary is to repeat the timing a few times and use the best time. The -r option is good for this; the default of 3 repetitions is probably enough in most cases. On Unix, you can use clock() to measure CPU time. Note: there is a certain baseline overhead associated with executing a pass statement. The code here doesn't try to hide it, but you should be aware of it. The baseline overhead can be measured by invoking the program without arguments. The baseline overhead differs between Python versions! Also, to fairly compare older Python versions to Python 2.3, you may want to use python -O for the older versions to avoid timing SET_LINENO instructions. i����Nt Timers <timeit-src>i@B i t win32s� def inner(_it, _timer%(init)s): %(setup)s _t0 = _timer() for _i in _it: %(stmt)s _t1 = _timer() return _t1 - _t0 c C s | j d d d | � S( s* Helper to reindent a multi-line statement.s t ( t replace( t srct indent( ( s /usr/lib64/python2.7/timeit.pyt reindentZ s c s | � f d � } | S( s? Create a timer function. Used if the "statement" is a callable.c s9 � � | � } x | D] } | � q W| � } | | S( N( ( t _itt _timert _funct _t0t _it _t1( t setup( s /usr/lib64/python2.7/timeit.pyt inner` s ( ( R t funcR ( ( R s /usr/lib64/python2.7/timeit.pyt _template_func^ s c B sG e Z d Z d d e d � Z d d � Z e d � Z e e d � Z RS( sI Class for timing execution speed of small code snippets. The constructor takes a statement to be timed, an additional statement used for setup, and a timer function. Both statements default to 'pass'; the timer function is platform-dependent (see module doc string). To measure the execution time of the first statement, use the timeit() method. The repeat() method is a convenience to call timeit() multiple times and return a list of results. The statements may contain newlines, as long as they don't contain multi-line string literals. t passc s� | | _ i � e | e � r6e | e � rX e | e d � e | d | e d � n e | e d � e | d � } e | e � r� e | d � } e i | d 6| d 6d d 6} nG e | d � r� e i | d 6d d 6d d 6} | � d <n e d � � | | _ e | e d � } | e � � U� d | _ n� e | d � r�d | _ e | e � rx| � � � f d � } n e | d � s�e d � � n e | | � | _ n e d � � d S( s# Constructor. See class doc string.t execs i i t stmtR t t initt __call__s _setup()s , _setup=_setupt _setups& setup is neither a string nor callableR c s � e � � Ud S( N( t globals( ( R t ns( s /usr/lib64/python2.7/timeit.pyR � s s% stmt is neither a string nor callableN( t timert isinstancet basestringt compilet dummy_src_nameR t templatet hasattrt ValueErrorR R R t NoneR ( t selfR R R R t code( ( R R s /usr/lib64/python2.7/timeit.pyt __init__y s: " c C sl d d l } d d l } | j d k rX t | j � d | j j d � t f | j t <n | j d | � d S( s� Helper to print a traceback from the timed code. Typical use: t = Timer(...) # outside the try/except try: t.timeit(...) # or t.repeat(...) except: t.print_exc() The advantage over the standard traceback is that source lines in the compiled template will be displayed. The optional file argument directs where the traceback is sent; it defaults to sys.stderr. i����Ns t file( t linecachet tracebackR R" t lent splitR t cachet print_exc( R# R& R' R( ( ( s /usr/lib64/python2.7/timeit.pyR, � s c C sr t r t j d | � } n d g | } t j � } t j � z | j | | j � } Wd | rm t j � n X| S( s� Time 'number' executions of the main statement. To be precise, this executes the setup statement once, and then returns the time it takes to execute the main statement a number of times, as a float measured in seconds. The argument is the number of times through the loop, defaulting to one million. The main statement, the setup statement and the timer function to be used are passed to the constructor. N( t itertoolst repeatR" t gct isenabledt disableR R t enable( R# t numbert itt gcoldt timing( ( s /usr/lib64/python2.7/timeit.pyt timeit� s c C s= g } x0 t | � D]" } | j | � } | j | � q W| S( s� Call timeit() a few times. This is a convenience function that calls the timeit() repeatedly, returning a list of results. The first argument specifies how many times to call timeit(), defaulting to 3; the second argument specifies the timer argument, defaulting to one million. Note: it's tempting to calculate mean and standard deviation from the result vector and report these. However, this is not very useful. In a typical case, the lowest value gives a lower bound for how fast your machine can run the given code snippet; higher values in the result vector are typically not caused by variability in Python's speed, but by other processes interfering with your timing accuracy. So the min() of the result is probably the only number you should be interested in. After that, you should look at the entire vector and apply common sense rather than statistics. ( t rangeR7 t append( R# R. R3 t rt it t( ( s /usr/lib64/python2.7/timeit.pyR. � s N( t __name__t __module__t __doc__t default_timerR% R" R, t default_numberR7 t default_repeatR. ( ( ( s /usr/lib64/python2.7/timeit.pyR i s % R c C s t | | | � j | � S( sC Convenience function to create Timer object and call timeit method.( R R7 ( R R R R3 ( ( s /usr/lib64/python2.7/timeit.pyR7 � s c C s t | | | � j | | � S( sC Convenience function to create Timer object and call repeat method.( R R. ( R R R R. R3 ( ( s /usr/lib64/python2.7/timeit.pyR. � s c C s� | d k r t j d } n d d l } y4 | j | d d d d d d d d g � \ } } Wn! | j k r } | GHd GHd SXt } d j | � p� d } d } g } t } d } d } x� | D]� \ } } | d, k r� t | � } n | d- k r| j | � n | d. k r3t | � } | d k r3d } q3n | d/ k rKt j } n | d0 k rct j } n | d1 k r�| r�| d 7} n | d 7} n | d2 k r� t Gd Sq� Wd j | � p�d } d d l } t j j d | j � | d k r�| | � } n t | | | � } | d k r�xw t d d � D]c } d | } y | j | � } Wn | j � d SX| rzd! | | | f GHn | d" k r'Pq'q'Wn y | j | | � } Wn | j � d SXt | � } | r d# Gd$ j g | D] } d% | | f ^ q�� GHn d& | G| d' | } | d( k r7d) | | | f GHnG | d( } | d( k rbd* | | | f GHn | d( } d+ | | | f GHd S(3 s� Main program, used when run as a script. The optional 'args' argument specifies the command line to be parsed, defaulting to sys.argv[1:]. The return value is an exit code to be passed to sys.exit(); it may be None to indicate success. When an exception happens during timing, a traceback is printed to stderr and the return value is 1. Exceptions at other times (including the template compilation) are not caught. '_wrap_timer' is an internal interface used for unit testing. If it is not None, it must be a callable that accepts a timer function and returns another timer function (used for unit testing). i i����Ns n:s:r:tcvhs number=s setup=s repeat=t timet clockt verboset helps# use -h/--help for command line helpi s R i i s -ns --numbers -ss --setups -rs --repeats -ts --times -cs --clocks -vs --verboses -hs --helpi s %d loops -> %.*g secsg�������?s raw times:R s %.*gs %d loops,g ��.Ai� s best of %d: %.*g usec per loops best of %d: %.*g msec per loops best of %d: %.*g sec per loop( s -ns --number( s -ss --setup( s -rs --repeat( s -ts --time( s -cs --clock( s -vs --verbose( s -hs --help( R" t syst argvt getoptt errorR@ t joinRB t intR9 RC RD R? t ost patht insertt curdirR R8 R7 R, R. t min( t argst _wrap_timerRI t optst errR R R3 R R. RE t precisiont ot aRM R< R; t xR: t bestt usect msect sec( ( s /usr/lib64/python2.7/timeit.pyt main� s� 2 t __main__( ( R? R/ RG RC R- t ImportErrorR" t __all__R RA RB t platformRD R@ R R R R R7 R. R^ R= t exit( ( ( s /usr/lib64/python2.7/timeit.pyt <module>5 s2 � b
SAVE
CANCEL