We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
write-started
write-started is emitted in Builder.write (here), but LatexBuilder overrides write and does not call super() (here).
Builder.write
LatexBuilder
write
super()
In conf, add extensions = ["foo"]. For foo.py, put:
extensions = ["foo"]
foo.py
import sys def setup(app): app.connect("write-started", lambda *x: sys.exit(1))
sphinx-build -Eb html will terminate building early. sphinx-build -Eb latex will complete building normally.
sphinx-build -Eb html
sphinx-build -Eb latex
Platform: win32; (Windows-10-10.0.22631-SP0) Python version: 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)]) Python implementation: CPython Sphinx version: 7.4.7 Docutils version: 0.20.1 Jinja2 version: 3.1.2 Pygments version: 2.18.0
No response
The text was updated successfully, but these errors were encountered:
You can put
def setup(app): app.connect("write-started", lambda *x: sys.exit(1))
directly at end of conf.py.
Same behavior as latex observed with texinfo, singlehtml and man builders.
Sorry, something went wrong.
cc @chrisjsewell as the author of that event
Builder.build
as the author of that event
but not the author of the "tweak" 😏; e536eb9
Builder.write()
Successfully merging a pull request may close this issue.
Describe the bug
write-started
is emitted inBuilder.write
(here), butLatexBuilder
overrideswrite
and does not callsuper()
(here).How to Reproduce
In conf, add
extensions = ["foo"]
. Forfoo.py
, put:sphinx-build -Eb html
will terminate building early.sphinx-build -Eb latex
will complete building normally.Environment Information
Sphinx extensions
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: