From 53017caa5c91ddb144c5d4c8203fa38254dd5585 Mon Sep 17 00:00:00 2001
From: "Miss Islington (bot)"
 <31488909+miss-islington@users.noreply.github.com>
Date: Thu, 23 Sep 2021 14:38:44 -0700
Subject: [PATCH] [docs] Update documentation for
 `multiprocessing.get_start_method` (GH-18170) (GH-28533)

(cherry picked from commit af90b5498b8c6acd67b50fdad007d26dfd1c5823)

Co-authored-by: Sam Sneddon <me@gsnedders.com>
---
 Doc/library/multiprocessing.rst | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst
index 945ac42b2fbb37..fbb3f192f7d6ed 100644
--- a/Doc/library/multiprocessing.rst
+++ b/Doc/library/multiprocessing.rst
@@ -1029,7 +1029,13 @@ Miscellaneous
 
    The return value can be ``'fork'``, ``'spawn'``, ``'forkserver'``
    or ``None``.  ``'fork'`` is the default on Unix, while ``'spawn'`` is
-   the default on Windows.
+   the default on Windows and macOS.
+
+.. versionchanged:: 3.8
+
+   On macOS, the *spawn* start method is now the default.  The *fork* start
+   method should be considered unsafe as it can lead to crashes of the
+   subprocess. See :issue:`33725`.
 
    .. versionadded:: 3.4