66msgstr ""
77"Project-Id-Version : Python 3.13\n "
88"Report-Msgid-Bugs-To : \n "
9- "POT-Creation-Date : 2025-03-02 00:15 +0000\n "
9+ "POT-Creation-Date : 2025-08-17 00:18 +0000\n "
1010"PO-Revision-Date : 2018-05-23 16:08+0000\n "
1111"Last-Translator : Adrian Liaw <adrianliaw2000@gmail.com>\n "
1212"Language-Team : Chinese - TAIWAN (https://github.com/python/python-docs-zh- "
@@ -53,21 +53,20 @@ msgstr ""
5353
5454#: ../../library/profile.rst:33
5555msgid ""
56- ":mod:`profile`, a pure Python module whose interface is imitated "
57- "by :mod:`cProfile`, but which adds significant overhead to profiled "
58- "programs. If you're trying to extend the profiler in some way, the task "
59- "might be easier with this module. Originally designed and written by Jim "
60- "Roskind."
56+ ":mod:`profile`, a pure Python module whose interface is imitated by :mod:"
57+ "`cProfile`, but which adds significant overhead to profiled programs. If "
58+ "you're trying to extend the profiler in some way, the task might be easier "
59+ "with this module. Originally designed and written by Jim Roskind."
6160msgstr ""
6261
6362#: ../../library/profile.rst:40
6463msgid ""
6564"The profiler modules are designed to provide an execution profile for a "
66- "given program, not for benchmarking purposes (for that, there "
67- "is :mod: `timeit` for reasonably accurate results). This particularly "
68- "applies to benchmarking Python code against C code: the profilers introduce "
69- "overhead for Python code, but not for C-level functions, and so the C code "
70- "would seem faster than any Python one."
65+ "given program, not for benchmarking purposes (for that, there is :mod: "
66+ "`timeit` for reasonably accurate results). This particularly applies to "
67+ "benchmarking Python code against C code: the profilers introduce overhead "
68+ "for Python code, but not for C-level functions, and so the C code would seem "
69+ "faster than any Python one."
7170msgstr ""
7271
7372#: ../../library/profile.rst:51
@@ -613,21 +612,20 @@ msgid ""
613612"printout to fit within (close to) 80 columns. This method modifies the "
614613"object, and the stripped information is lost. After performing a strip "
615614"operation, the object is considered to have its entries in a \" random\" "
616- "order, as it was just after object initialization and loading. "
617- "If :meth: `~pstats.Stats.strip_dirs` causes two function names to be "
618- "indistinguishable (they are on the same line of the same filename, and have "
619- "the same function name), then the statistics for these two entries are "
620- "accumulated into a single entry."
615+ "order, as it was just after object initialization and loading. If :meth: "
616+ "`~pstats.Stats.strip_dirs` causes two function names to be indistinguishable "
617+ "(they are on the same line of the same filename, and have the same function "
618+ "name), then the statistics for these two entries are accumulated into a "
619+ "single entry."
621620msgstr ""
622621
623622#: ../../library/profile.rst:388
624623msgid ""
625624"This method of the :class:`Stats` class accumulates additional profiling "
626625"information into the current profiling object. Its arguments should refer "
627- "to filenames created by the corresponding version of :func:`profile.run` "
628- "or :func:`cProfile.run`. Statistics for identically named (re: file, line, "
629- "name) functions are automatically accumulated into single function "
630- "statistics."
626+ "to filenames created by the corresponding version of :func:`profile.run` or :"
627+ "func:`cProfile.run`. Statistics for identically named (re: file, line, name) "
628+ "functions are automatically accumulated into single function statistics."
631629msgstr ""
632630
633631#: ../../library/profile.rst:398
@@ -818,12 +816,12 @@ msgstr "``'tottime'``"
818816msgid ""
819817"Note that all sorts on statistics are in descending order (placing most time "
820818"consuming items first), where as name, file, and line number searches are in "
821- "ascending order (alphabetical). The subtle distinction between "
822- "``SortKey. NFL`` and ``SortKey.STDNAME`` is that the standard name is a sort "
823- "of the name as printed, which means that the embedded line numbers get "
824- "compared in an odd way. For example, lines 3, 20, and 40 would (if the file "
825- "names were the same) appear in the string order 20, 3 and 40. In contrast, "
826- "``SortKey. NFL`` does a numeric compare of the line numbers. In fact, "
819+ "ascending order (alphabetical). The subtle distinction between ``SortKey. "
820+ "NFL`` and ``SortKey.STDNAME`` is that the standard name is a sort of the "
821+ "name as printed, which means that the embedded line numbers get compared in "
822+ "an odd way. For example, lines 3, 20, and 40 would (if the file names were "
823+ "the same) appear in the string order 20, 3 and 40. In contrast, ``SortKey. "
824+ "NFL`` does a numeric compare of the line numbers. In fact, "
827825"``sort_stats(SortKey.NFL)`` is the same as ``sort_stats(SortKey.NAME, "
828826"SortKey.FILENAME, SortKey.LINE)``."
829827msgstr ""
@@ -856,10 +854,9 @@ msgstr ""
856854
857855#: ../../library/profile.rst:493
858856msgid ""
859- "The order of the printing is based on the "
860- "last :meth:`~pstats.Stats.sort_stats` operation done on the object (subject "
861- "to caveats in :meth:`~pstats.Stats.add` "
862- "and :meth:`~pstats.Stats.strip_dirs`)."
857+ "The order of the printing is based on the last :meth:`~pstats.Stats."
858+ "sort_stats` operation done on the object (subject to caveats in :meth:"
859+ "`~pstats.Stats.add` and :meth:`~pstats.Stats.strip_dirs`)."
863860msgstr ""
864861
865862#: ../../library/profile.rst:498
@@ -868,7 +865,7 @@ msgid ""
868865"significant entries. Initially, the list is taken to be the complete set of "
869866"profiled functions. Each restriction is either an integer (to select a "
870867"count of lines), or a decimal fraction between 0.0 and 1.0 inclusive (to "
871- "select a percentage of lines), or a string that will interpreted as a "
868+ "select a percentage of lines), or a string that will be interpreted as a "
872869"regular expression (to pattern match the standard name that is printed). If "
873870"several restrictions are provided, then they are applied sequentially. For "
874871"example::"
@@ -1169,8 +1166,8 @@ msgstr ""
11691166#: ../../library/profile.rst:713
11701167msgid ""
11711168"Python 3.3 adds several new functions in :mod:`time` that can be used to "
1172- "make precise measurements of process or wall-clock time. For example, "
1173- "see : func:`time.perf_counter`."
1169+ "make precise measurements of process or wall-clock time. For example, see : "
1170+ "func:`time.perf_counter`."
11741171msgstr ""
11751172
11761173#: ../../library/profile.rst:16
0 commit comments