Skip to content

[3.13] gh-131788: make resource_tracker re-entrant safe (GH-131787) #137738

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

Merged
merged 1 commit into from
Aug 14, 2025

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Aug 13, 2025

  • make resource_tracker re-entrant safe
  • Update Lib/multiprocessing/resource_tracker.py
  • trim trailing whitespace
  • use f-string and args = [x, *y, z]
  • raise self._reentrant_call_error

(cherry picked from commit f24a012)

Co-authored-by: Thomas Grainger [email protected]
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>
Co-authored-by: Gregory P. Smith [email protected]

* make resource_tracker re-entrant safe
* Update Lib/multiprocessing/resource_tracker.py
* trim trailing whitespace
* use f-string and args = [x, *y, z]
* raise self._reentrant_call_error

---------
(cherry picked from commit f24a012)

Co-authored-by: Thomas Grainger <[email protected]>
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>
Co-authored-by: Gregory P. Smith <[email protected]>
@ngoldbaum
Copy link
Contributor

It looks like this backport is causing some breakage in loky, which is used by joblib. Ping @Yhg1s - not sure if this might be considered a bug in 3.13.7.

@gpshead
Copy link
Member

gpshead commented Aug 20, 2025

it'd be useful to link to specifics examples, but please do so on the issue rather than on this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants