Kaydet (Commit) d382bfc9 authored tarafından Brett Cannon's avatar Brett Cannon

Move importlib.test.benchmark to Tools/importbench to make it more

visible and to place it with other micro-benchmarks (e.g.
stringbench).
üst 45a5e3af
...@@ -154,6 +154,8 @@ Extension Modules ...@@ -154,6 +154,8 @@ Extension Modules
Tools/Demos Tools/Demos
----------- -----------
- Move importlib.test.benchmark to Tools/importbench.
- Issue #12605: The gdb hooks for debugging CPython (within Tools/gdb) have - Issue #12605: The gdb hooks for debugging CPython (within Tools/gdb) have
been enhanced to show information on more C frames relevant to CPython within been enhanced to show information on more C frames relevant to CPython within
the "py-bt" and "py-bt-full" commands: the "py-bt" and "py-bt-full" commands:
......
Importbench is a set of micro-benchmarks for various import scenarios.
It should not be used as an overall benchmark of import performance, but rather
an easy way to measure impact of possible code changes. For a real-world
benchmark of import, use the normal_startup benchmark from
hg.python.org/benchmarks.
...@@ -4,8 +4,8 @@ The assumption is made that this benchmark is run in a fresh interpreter and ...@@ -4,8 +4,8 @@ The assumption is made that this benchmark is run in a fresh interpreter and
thus has no external changes made to import-related attributes in sys. thus has no external changes made to import-related attributes in sys.
""" """
from . import util from test.test_importlib import util
from .source import util as source_util from test.test_importlib.source import util as source_util
import decimal import decimal
import imp import imp
import importlib import importlib
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment