Skip to content

Doc nits for bpo-16500 #1841

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
May 28, 2017
Merged

Doc nits for bpo-16500 #1841

merged 2 commits into from
May 28, 2017

Conversation

pitrou
Copy link
Member

@pitrou pitrou commented May 28, 2017

No description provided.

@mention-bot
Copy link

@pitrou, thanks for your PR! By analyzing the history of the files in this pull request, we identified @rhettinger, @benjaminp and @serhiy-storchaka to be potential reviewers.

@pitrou pitrou added the trivial label May 28, 2017
Copy link
Member

@serhiy-storchaka serhiy-storchaka left a comment

Choose a reason for hiding this comment

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

PyOS_AfterFork() also is mentioned in Doc/c-api/init.rst.

@pitrou
Copy link
Member Author

pitrou commented May 28, 2017

Thanks @serhiy-storchaka, for some reason I had overlooked it.

Copy link
Member

@serhiy-storchaka serhiy-storchaka left a comment

Choose a reason for hiding this comment

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

LGTM.

But maybe Doc/c-api/init.rst needs more updates.

@@ -564,7 +564,7 @@ Additionally, when extending or embedding Python, calling :c:func:`fork`
directly rather than through :func:`os.fork` (and returning to or calling
into Python) may result in a deadlock by one of Python's internal locks
being held by a thread that is defunct after the fork.
:c:func:`PyOS_AfterFork` tries to reset the necessary locks, but is not
:c:func:`PyOS_AfterFork_Child` tries to reset the necessary locks, but is not
Copy link
Member

Choose a reason for hiding this comment

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

Is it worth to update the first part of this paragraph according to new API?

Copy link
Member Author

Choose a reason for hiding this comment

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

Which part exactly?

Copy link
Member

Choose a reason for hiding this comment

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

"there is no way to inform Python of additional (non-Python) locks that need to be acquired before or reset after a fork" and mentioning pthread_atfork.

@pitrou pitrou merged commit f7ecfac into python:master May 28, 2017
ma8ma added a commit to ma8ma/cpython that referenced this pull request Jun 13, 2017
Resolve conflicts:
f7ecfac Doc nits for bpo-16500 (python#1841)
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.

4 participants