Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

gh-143057: avoid lock in tracemalloc APIs when it is not enabled#143065

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
kumaraditya303 merged 4 commits intopython:mainfromkumaraditya303:tracemalloc
Dec 22, 2025

Conversation

@kumaraditya303
Copy link
Contributor

@kumaraditya303kumaraditya303 commentedDec 22, 2025•
edited by bedevere-appbot
Loading

@kumaraditya303kumaraditya303 marked this pull request as ready for reviewDecember 22, 2025 12:00
…e-143057.Majsre.rstCo-authored-by: T. Wouters <thomas@python.org>
@kumaraditya303
Copy link
ContributorAuthor

@Yhg1s Should this be backported to 3.14?

@ngoldbaum
Copy link
Contributor

ngoldbaum commentedDec 22, 2025•
edited
Loading

@Yhg1s Should this be backported to 3.14?

I think so yes. I like@colesbury's rule of thumb for this, I hope he doesn't mind me quoting something he said on discord:

I think it's often worth it to backport small changes that avoid scaling bottlenecks if we have a bug report or think it's likely that people are running into them.

I think it's not worth backporting small performance improvements.

Roughly: if something is accidentally O(N^2), it's a bug. If something is 10% faster, it's a performance improvement.

Copy link
Contributor

@colesburycolesbury left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

LGTM as well

@kumaraditya303kumaraditya303 added performancePerformance or resource usage topic-free-threading needs backport to 3.14bugs and security fixes labelsDec 22, 2025
@kumaraditya303kumaraditya303 merged commite728b00 intopython:mainDec 22, 2025
52 checks passed
@miss-islington-app
Copy link

Thanks@kumaraditya303 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14.
🐍🍒⛏🤖

@kumaraditya303kumaraditya303 deleted the tracemalloc branchDecember 22, 2025 15:38
miss-islington pushed a commit to miss-islington/cpython that referenced this pull requestDec 22, 2025
… enabled (pythonGH-143065)(cherry picked from commite728b00)Co-authored-by: Kumar Aditya <kumaraditya@python.org>
@bedevere-app
Copy link

GH-143071 is a backport of this pull request to the3.14 branch.

@bedevere-appbedevere-appbot removed the needs backport to 3.14bugs and security fixes labelDec 22, 2025
kumaraditya303 added a commit that referenced this pull requestDec 22, 2025
…t enabled (GH-143065) (#143071)gh-143057: avoid locking in `tracemalloc` C-APIs when it is not enabled (GH-143065)(cherry picked from commite728b00)Co-authored-by: Kumar Aditya <kumaraditya@python.org>
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@colesburycolesburycolesbury approved these changes

@Yhg1sYhg1sYhg1s approved these changes

Assignees

No one assigned

Labels

performancePerformance or resource usagetopic-free-threading

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@kumaraditya303@ngoldbaum@colesbury@Yhg1s
[8]ページ先頭
©2009-2026 Movatter.jp