-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
gh-142651: Make call_count of Mock thread safe #142656
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
758084c to
816a404
Compare
76816a8 to
29578a9
Compare
Misc/NEWS.d/next/Library/2025-12-13-06-17-44.gh-issue-142651.ZRtBu4.rst
Outdated
Show resolved
Hide resolved
…RtBu4.rst Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
…into fix-issue-142651
fb7eab9 to
8e2348c
Compare
picnixz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
| import concurrent.futures | ||
|
|
||
| from test.support import threading_helper | ||
| from test.support import setswitchinterval, threading_helper |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes me think that we should have this as a context manager instead but this is a separate issue. I'll do it tomorrow myself.
gh-142651: Make call_count of Mock thread safe