Skip to content

[pull] main from python:main #511

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.

Sign up for GitHub

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
pull merged 2 commits into from
Dec 1, 2025
Merged

[pull] main from python:main #511

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
981ce0c
gh-142066: Fix grammar in multiprocessing Pipes and Queues (GH-142121)
tadejmagajna Dec 1, 2025
3e2c557
gh-141473: Document not calling Popen.wait after Popen.communicate ti…
gpshead Dec 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Doc/library/multiprocessing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -832,8 +832,8 @@ raising an exception.

One difference from other Python queue implementations, is that :mod:`multiprocessing`
queues serializes all objects that are put into them using :mod:`pickle`.
The object return by the get method is a re-created object that does not share memory
with the original object.
The object returned by the get method is a re-created object that does not share
memory with the original object.

Note that one can also create a shared queue by using a manager object -- see
:ref:`multiprocessing-managers`.
Expand Down
5 changes: 5 additions & 0 deletions Doc/library/subprocess.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -846,6 +846,11 @@ Instances of the :class:`Popen` class have the following methods:
proc.kill()
outs, errs = proc.communicate()

After a call to :meth:`~Popen.communicate` raises :exc:`TimeoutExpired`, do
not call :meth:`~Popen.wait`. Use an additional :meth:`~Popen.communicate`
call to finish handling pipes and populate the :attr:`~Popen.returncode`
attribute.

.. note::

The data read is buffered in memory, so do not use this method if the data
Expand Down
Loading