From 2813d1a968d6f694514a0053d094c0da9ea4863b Mon Sep 17 00:00:00 2001 From: David Wilson Date: Sun, 25 Mar 2018 14:58:20 +0545 Subject: [PATCH] docs: update --- docs/api.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/api.rst b/docs/api.rst index e49704fd..7f488f23 100644 --- a/docs/api.rst +++ b/docs/api.rst @@ -528,8 +528,9 @@ Router Class For long-lived processes, :py:meth:`local` is always better as it guarantees a pristine interpreter state that inherited little from the parent. Forking should only be used in performance-sensitive scenarios - where short-lived children are spawned, and only after accounting for - all the bad things possible as a result of, at a minimum: + where short-lived children must be spawned to isolate potentially buggy + code, and only after accounting for all the bad things possible as a + result of, at a minimum: * Files open in the parent remaining open in the child, causing the lifetime of the underlying object to be extended