summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTakeshi KOMIYA <i.tkomiya@gmail.com>2021-04-18 15:22:19 +0900
committerGitHub <noreply@github.com>2021-04-18 15:22:19 +0900
commit8ec937d4c965b0abd4c2c77d139a884455f907ae (patch)
treefb4b29f102bd336f7775e2f9ef237ecc6ecf9bee
parent226c70c58b80992b0cbbe49e41e160c70bb8f621 (diff)
parent02016c0ef25f6a521aae789727487e0bbc71014a (diff)
downloadsphinx-git-8ec937d4c965b0abd4c2c77d139a884455f907ae.tar.gz
Merge pull request #9050 from tk0miya/8829_whats_parallel_read_safe
Close #8829: doc: Update description of paralle-read-safe
-rw-r--r--doc/extdev/index.rst16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/extdev/index.rst b/doc/extdev/index.rst
index ad04951f3..d9c04f413 100644
--- a/doc/extdev/index.rst
+++ b/doc/extdev/index.rst
@@ -171,10 +171,26 @@ as metadata of the extension. Metadata keys currently recognized are:
source files can be used when the extension is loaded. It defaults to
``False``, i.e. you have to explicitly specify your extension to be
parallel-read-safe after checking that it is.
+
+ .. note:: The *parallel-read-safe* extension must satisfy the following
+ conditions:
+
+ * The core logic of the extension is parallely executable during
+ the reading phase.
+ * It has event handlers for :event:`env-merge-info` and
+ :event:`env-purge-doc` events if it stores dataa to the build
+ environment object (env) during the reading phase.
+
* ``'parallel_write_safe'``: a boolean that specifies if parallel writing of
output files can be used when the extension is loaded. Since extensions
usually don't negatively influence the process, this defaults to ``True``.
+ .. note:: The *parallel-write-safe* extension must satisfy the following
+ conditions:
+
+ * The core logic of the extension is parallely executable during
+ the writing phase.
+
APIs used for writing extensions
--------------------------------