-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
bpo-32362: Fix references to non-existent multiprocessing.Connection() #6223
bpo-32362: Fix references to non-existent multiprocessing.Connection() #6223
Conversation
Would the |
Good suggestion. That directive is aimed at this issue; I've made that change. |
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.
Thank you. But such minor documentation changes usually don't need a news entry.
Shall I remove the news entry? I put it in because I thought the bedevere-bot would issue me a red check mark. |
This warning can be silenced. |
Right-o. |
Doc/library/multiprocessing.rst
Outdated
@@ -2269,7 +2274,7 @@ Listeners and Clients | |||
:synopsis: API for dealing with sockets. | |||
|
|||
Usually message passing between processes is done using queues or by using | |||
:class:`~multiprocessing.Connection` objects returned by | |||
:class:`~multiprocessing.connection.Connection` objects returned by |
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.
Can be just :class:`Connection`
.
Doc/library/multiprocessing.rst
Outdated
@@ -2299,7 +2304,7 @@ multiple connections at the same time. | |||
.. function:: Client(address[, family[, authkey]]) | |||
|
|||
Attempt to set up a connection to the listener which is using address | |||
*address*, returning a :class:`~multiprocessing.Connection`. | |||
*address*, returning a :class:`~multiprocessing.connection.Connection`. |
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.
Can be just :class:`Connection`
.
Doc/library/multiprocessing.rst
Outdated
@@ -2349,8 +2354,8 @@ multiple connections at the same time. | |||
.. method:: accept() | |||
|
|||
Accept a connection on the bound socket or named pipe of the listener | |||
object and return a :class:`~multiprocessing.Connection` object. If | |||
authentication is attempted and fails, then | |||
object and return a :class:`~multiprocessing.connection.Connection` object. |
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.
Can be just :class:`Connection`
.
Doc/library/multiprocessing.rst
Outdated
@@ -2509,8 +2514,8 @@ an ``'AF_PIPE'`` address rather than an ``'AF_UNIX'`` address. | |||
Authentication keys | |||
~~~~~~~~~~~~~~~~~~~ | |||
|
|||
When one uses :meth:`Connection.recv <multiprocessing.Connection.recv>`, the | |||
data received is automatically | |||
When one uses :meth:`Connection.recv <multiprocessing.connection.Connection.recv>`, |
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.
Can be just :meth:`Connection.recv`
.
@@ -1021,6 +1022,8 @@ Miscellaneous | |||
Connection Objects | |||
~~~~~~~~~~~~~~~~~~ | |||
|
|||
.. currentmodule:: multiprocessing.connection |
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.
In the line below
Therefore, unless the connection object was produced using :func:`Pipe` you
:func:`Pipe`
is not converted to a link because the current module is multiprocessing.connection
.
Thanks for looking over this. I've incorporated your suggestions. |
Thank you for your contribution @bbayles! |
Thanks @bbayles for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 2.7, 3.6, 3.7. |
pythonGH-6223) (cherry picked from commit 9f3535c) Co-authored-by: Bo Bayles <bbayles@gmail.com>
GH-6639 is a backport of this pull request to the 3.7 branch. |
Sorry, @bbayles and @serhiy-storchaka, I could not cleanly backport this to |
pythonGH-6223) (cherry picked from commit 9f3535c) Co-authored-by: Bo Bayles <bbayles@gmail.com>
GH-6640 is a backport of this pull request to the 3.6 branch. |
Many thanks for the guidance on this, @serhiy-storchaka . While you've got the |
…ction() (pythonGH-6223). (cherry picked from commit 9f3535c) Co-authored-by: Bo Bayles <bbayles@gmail.com>
GH-6646 is a backport of this pull request to the 2.7 branch. |
This PR fixes references to
multiprocessing.Connection()
in themultiprocessing
docs - they should bemultiprocessing.connection.Connection()
.We set the
module
currentmodule
directive such that Sphinx renders the class name correctly (here),butsincemodule:: multiprocessing.connection
is already used once (here), we also set.noindex
to avoid messing with the document structurehttps://bugs.python.org/issue32362