gh-132969 Fix Sphinx Lint error

ogbiggles · ogbiggles · commit 709d9fd0d265 · 2025-05-08T23:26:17.000-04:00
diff --git a/Misc/NEWS.d/next/Library/2025-04-30-19-32-18.gh-issue-132969.EagQ3G.rst b/Misc/NEWS.d/next/Library/2025-04-30-19-32-18.gh-issue-132969.EagQ3G.rst
@@ -1 +1 @@
-Prevent the `ProcessPoolExecutor` executor thread from tying to adjust worker processes after `shutdown` is called and object state has already been reset. Calling `shutdown` with `wait=False` resets the state of the `ProcessPoolExecutor` while still leaving the executor thread running. A combination of conditions including a worker process having terminated abormally and `shutdown(wait=False)` resulted in an exception when the executor thread tried to replace dead workers, and additionally the process could also potentially hang.
+Prevent the ProcessPoolExecutor executor thread from tying to adjust worker processes after shutdown is called and object state has already been reset. Calling shutdown with wait=False resets the state of the ProcessPoolExecutor while still leaving the executor thread running. A combination of conditions including a worker process having terminated abormally and shutdown(wait=False) resulted in an exception when the executor thread tried to replace dead workers, and additionally the process could also potentially hang.

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		-Prevent the `ProcessPoolExecutor` executor thread from tying to adjust worker processes after `shutdown` is called and object state has already been reset. Calling `shutdown` with `wait=False` resets the state of the `ProcessPoolExecutor` while still leaving the executor thread running. A combination of conditions including a worker process having terminated abormally and `shutdown(wait=False)` resulted in an exception when the executor thread tried to replace dead workers, and additionally the process could also potentially hang.
	`1`	+Prevent the ProcessPoolExecutor executor thread from tying to adjust worker processes after shutdown is called and object state has already been reset. Calling shutdown with wait=False resets the state of the ProcessPoolExecutor while still leaving the executor thread running. A combination of conditions including a worker process having terminated abormally and shutdown(wait=False) resulted in an exception when the executor thread tried to replace dead workers, and additionally the process could also potentially hang.