]> git.ipfire.org Git - thirdparty/Python/cpython.git/commitdiff
[3.14] gh-137090: Remove redundant statement in ``Doc/library/concurrent.interpreters...
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Fri, 25 Jul 2025 16:08:28 +0000 (18:08 +0200)
committerGitHub <noreply@github.com>
Fri, 25 Jul 2025 16:08:28 +0000 (19:08 +0300)
gh-137090: Remove redundant statement in ``Doc/library/concurrent.interpreters.rst`` (GH-137091)
(cherry picked from commit 1e69cd1634e4f0f8c375be85d11925bd12deef23)

Co-authored-by: soolabettu <17737361+soolabettu@users.noreply.github.com>
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Doc/library/concurrent.interpreters.rst

index be9d565f8e0d38385d7dadf1ff7ec253afaf140b..41ea6af3b226e98569686678838de35db85cfb04 100644 (file)
@@ -134,7 +134,7 @@ makes them similar to processes, but they still enjoy in-process
 efficiency, like threads.
 
 All that said, interpreters do naturally support certain flavors of
-concurrency, as a powerful side effect of that isolation.
+concurrency.
 There's a powerful side effect of that isolation.  It enables a
 different approach to concurrency than you can take with async or
 threads.  It's a similar concurrency model to CSP or the actor model,