[4294668.857000000]Unknown #ˆl–ß=¿JJj"Tâ‚ ÆÚ¸)‹Fÿà ƒh¹ÂÁÀ ˆÄà „.¶/ÂÁÀauto ?÷a ´iŽrã@sÊdZddlZddlZddlZddlZddlZddlmZddlm Z ddl m Z ddl m Z gd¢ZGdd „d eeƒZe d d �Gd d „d ƒƒZe d d �Gdd„dƒƒZGdd„dƒZGdd„dƒZdd„Zdd„Zdd„Zdd„Zdd„Zdd„Zd d!„Zed"k�rÆddlZz ddlZWne�y,Yn0Gd#d$„d$ej ƒZ!e"ej#ƒd%k�r\ej#d%Z$ndZ$zPe!e$ƒZ%ej#d&d…D]Z&e% 'e&¡�qxe(d'e%j)d(�e% *¡e(d)e%j)d(�Wne+�yÄYn0dS)*z3Class for printing reports on profiled python code.éN)ÚEnum)Ú cmp_to_key)Ú dataclass)ÚDict)ÚStatsÚSortKeyÚFunctionProfileÚ StatsProfilec@s8eZdZdZdZdZdZdZdZdZ dZ d Z d d „Z d S) r)ÚcallsÚncalls)Ú cumulativeÚcumtime)ÚfilenameÚmoduleÚlineÚnameÚnflÚpcallsÚstdname)ÚtimeÚtottimecGs@|d}t ||¡}||_|dd…D]}||j|<q&||_|S©Nré)ÚstrÚ__new__Ú_value_Ú_value2member_map_Z _all_values)ÚclsÚvaluesÚvalueÚobjZ other_value©r!ú/usr/lib64/python3.9/pstats.pyr/s  zSortKey.__new__N) Ú__name__Ú __module__Ú __qualname__ZCALLSZ CUMULATIVEZFILENAMEZLINEÚNAMEZNFLZPCALLSZSTDNAMEZTIMErr!r!r!r"r$srT)Z unsafe_hashc@sFeZdZUeed<eed<eed<eed<eed<eed<eed<dS) rr rÚpercall_tottimer Úpercall_cumtimeÚ file_nameÚ line_numberN)r#r$r%ÚintÚ__annotations__Úfloatrr!r!r!r"r9s rc@s*eZdZUdZeed<eeefed<dS)r z0Class for keeping track of an item in inventory.Útotal_ttÚ func_profilesN) r#r$r%Ú__doc__r-r,rrrr!r!r!r"r Cs r c@sàeZdZdZddœdd„Zdd„Zdd „Zd d „Zd d „Zdd„Z ddddddddddddddœ Z dd„Z dd„Z dd„Z d d!„Zd"d#„Zd$d%„Zd&d'„Zd(d)„Zd*d+„Zd,d-„Zd.d/„Zd0d1„Zd9d3d4„Zd5d6„Zd7d8„ZdS):raÛThis class is used for creating reports from data generated by the Profile class. It is a "friend" of that class, and imports data either by direct access to members of Profile class, or by reading in a dictionary that was emitted (via marshal) from the Profile class. The big change from the previous Profiler (in terms of raw functionality) is that an "add()" method has been provided to combine Stats from several distinct profile runs. Both the constructor and the add() method now take arbitrarily many file names as arguments. All the print methods now take an argument that indicates how many lines to print. If the arg is a floating point number between 0 and 1.0, then it is taken as a decimal percentage of the available lines to be printed (e.g., .1 means print 10% of all available lines). If it is an integer, it is taken to mean the number of lines of data that you wish to have printed. The sort_stats() method now processes some additional options (i.e., in addition to the old -1, 0, 1, or 2 that are respectively interpreted as 'stdname', 'calls', 'time', and 'cumulative'). It takes either an arbitrary number of quoted strings or SortKey enum to select the sort order. For example sort_stats('time', 'name') or sort_stats(SortKey.TIME, SortKey.NAME) sorts on the major key of 'internal function time', and on the minor key of 'the name of the function'. Look at the two tables in sort_stats() and get_sort_arg_defs(self) for more examples. All methods return self, so you can string together commands like: Stats('foo', 'goo').strip_dirs().sort_stats('calls'). print_stats(5).print_callers(5) N)ÚstreamcGsF|ptj|_t|ƒsd}n|d}|dd…