Doc: Fix buf argument name in multiprocessing connection send_bytes recv_bytes_into #126603
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Documentation
The documentation for multiprocessing.connection.Connection.send_bytes says that the first argument is called
buffer
.When I run:
(On python 3.13)
In connection.py the argument is defined as
buf
notbuffer
.Indeed when I instead write
c1.send_bytes(buf=b'123')
, it runs without throwing an exception.The same is true of
recv_bytes_into
.Note: I did not raise an issue for this, because it is so trivial.
📚 Documentation preview 📚: https://cpython-previews--126603.org.readthedocs.build/