gh-84559: Remove the new multiprocessing warning, too disruptive. (#101551)

This reverts the core of #100618 while leaving relevant documentation
improvements and minor refactorings in place.

1 files changed, 0 insertions, 17 deletions

diff --git a/Lib/concurrent/futures/process.py b/Lib/concurrent/futures/process.py
index 257dd02..bee1624 100644
--- a/Lib/concurrent/futures/process.py
+++ b/Lib/concurrent/futures/process.py
@@ -57,7 +57,6 @@ from functools import partial
 import itertools
 import sys
 from traceback import format_exception
-import warnings
 
 
 _threads_wakeups = weakref.WeakKeyDictionary()
@@ -651,22 +650,6 @@ class ProcessPoolExecutor(_base.Executor):
                 mp_context = mp.get_context("spawn")
             else:
                 mp_context = mp.get_context()
-        if (mp_context.get_start_method() == "fork" and
-            mp_context == mp.context._default_context._default_context):
-            warnings.warn(
-                "The default multiprocessing start method will change "
-                "away from 'fork' in Python >= 3.14, per GH-84559. "
-                "ProcessPoolExecutor uses multiprocessing. "
-                "If your application requires the 'fork' multiprocessing "
-                "start method, explicitly specify that by passing a "
-                "mp_context= parameter. "
-                "The safest start method is 'spawn'.",
-                category=mp.context.DefaultForkDeprecationWarning,
-                stacklevel=2,
-            )
-            # Avoid the equivalent warning from multiprocessing itself via
-            # a non-default fork context.
-            mp_context = mp.get_context("fork")
         self._mp_context = mp_context
 
         # https://github.com/python/cpython/issues/90622