cpython - The Python programming language

	Commit message (Collapse)	Author	Age
*	gh-132553: Build the perf tool without buildid cache (GH-132663)	Pablo Galindo Salgado	13 days
\|
*	gh-132038: Make perf version check in test_perf_profiler more robust (#132039)	Itamar Oren	2025-04-03
\| \| \| \|	Should work also if the version string includes a commit hash, like `perf version 6.12.9.g242e6068fd5c`
*	gh-111178: Skip test_perf_profiler on function sanitizer (#132020)	Victor Stinner	2025-04-02
\| \| \|	Add 'function' parameter to check_sanitizer() of test.support.
*	gh-128515: Properly check for bolt in test_perf_profiler (#131058)	Pablo Galindo Salgado	2025-03-10
\|
*	gh-128515: Add BOLT build to CI (gh-128845)	Zanie Blue	2025-01-18
\|
*	gh-126255: Ignore warning about JIT being deactivated when perf support is ↵	mpage	2024-11-01
\| \| \| \| \| \| \| \| \| \| \|	active in `test_embed.InitConfigTests.test_initconfig_api` (#126302) Temporarily ignore warnings about JIT deactivation when perf support is active. This will be reverted as soon as a way is found to determine at run time whether the interpreter was built with JIT. Currently, this is not possible on Windows. Co-authored-by: Kirill Podoprigora <kirill.bast9@mail.ru> Co-authored-by: Ken Jin <28750310+Fidget-Spinner@users.noreply.github.com> Co-authored-by: Pablo Galindo <pablogsal@gmail.com>
*	gh-124613: Deactivate perf support in tests if the jit is set (#124794)	Pablo Galindo Salgado	2024-10-04
\| \| \| \| \|	gh-124613: Deactivate the JIT during perf tests Signed-off-by: Pablo Galindo <pablogsal@gmail.com>
*	gh-124613: Don't run perf tests in JIT builds (#124792)	Pablo Galindo Salgado	2024-09-30
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	* gh-124613: Don't run perf tests in JIT builds Signed-off-by: Pablo Galindo <pablogsal@gmail.com> * Apply suggestions from code review Co-authored-by: Victor Stinner <vstinner@python.org> --------- Signed-off-by: Pablo Galindo <pablogsal@gmail.com> Co-authored-by: Victor Stinner <vstinner@python.org>
*	test: fix _is_perf_version_at_least typo (#124199)	Sam James	2024-09-18
\|
*	gh-120417: Remove unused imports in tests (part 3) (#120631)	Victor Stinner	2024-06-17
\|
*	gh-118518: Check for perf version and not kernel version in ↵	Pablo Galindo Salgado	2024-05-07
\| \| \| \|	test_perf_profiler (#118640)
*	gh-118518: Rename `PYTHONPERFJITSUPPORT` and `-X perfjit` with underscores ↵	Hugo van Kemenade	2024-05-07
\| \| \| \|	(#118693)
*	gh-118518: Allow perf to work without frame pointers (#112254)	Pablo Galindo Salgado	2024-05-05
\|
*	GH-115802: Use the GHC calling convention in JIT code (GH-118287)	Brandt Bucher	2024-05-01
\|
*	gh-109587: Allow "precompiled" perf-trampolines to largely mitigate the cost ↵	gsallam	2023-10-27
\| \| \| \|	of enabling perf-trampolines (#109666)
*	gh-109580: Skip test_perf_profiler on ASAN build (#109584)	Victor Stinner	2023-09-19
\| \| \| \|	Skip test_perf_profiler if Python is built with ASAN, MSAN or UBSAN sanitizer. Python does crash randomly in this test on such build.
*	gh-103650: Fix perf maps address format (#103651)	Arthur Pastel	2023-05-07
\|
*	gh-96143: subprocess API %s/universal_newlines=/text=/g. (GH-96468)	Gregory P. Smith	2022-09-01
\| \| \| \| \|	minor missed test cleanup to use the modern API from the big review. Automerge-Triggered-By: GH:gpshead
*	gh-96143: Add some comments and minor fixes missed in the original PR (#96433)	Pablo Galindo Salgado	2022-08-30
\| \| \| \| \| \| \| \| \|	* gh-96132: Add some comments and minor fixes missed in the original PR * Update Doc/using/cmdline.rst Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com> Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com>
*	gh-96143: Allow Linux perf profiler to see Python calls (GH-96123)	Pablo Galindo Salgado	2022-08-30
	:warning: :warning: Note for reviewers, hackers and fellow systems/low-level/compiler engineers :warning: :warning: If you have a lot of experience with this kind of shenanigans and want to improve the first version, please make a PR against my branch or reach out by email or suggest code changes directly on GitHub. If you have any refinements or optimizations please, wait until the first version is merged before starting hacking or proposing those so we can keep this PR productive.