Skip to content

bpo-40221: Update ForkAwareThreadLock to use _at_fork_reinit #19477

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 2 commits into from
Apr 14, 2020

Conversation

corona10
Copy link
Member

@corona10 corona10 commented Apr 11, 2020

@@ -0,0 +1 @@
Update ForkAwareThreadLock to use _at_fork_reinit.
Copy link
Member

Choose a reason for hiding this comment

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

For such news entry, you should mention which module is modified. The user reading the NEWS entry has no idea, except maybe multiprocessing experts ;-)

For this specific change, honestly, I don't think that end users really care: I suggest to remove the NEWS entry. The change doesn't seem to fix any known crash, it's more a cleanup/refactoring.

Copy link
Member

@vstinner vstinner left a comment

Choose a reason for hiding this comment

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

LGTM if you remove the NEWS entry. But I also suggest to mention somehow multiprocessing in the commit message.

@vstinner
Copy link
Member

vstinner commented Apr 14, 2020

Commit message: for example, " bpo-40221: Update multiprocessing to use _at_fork_reinit".

@corona10 corona10 merged commit e194530 into python:master Apr 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants