Currently, ``test_nosearch`` depends on ``html_search_language='de'``
from a previous test and thus fails if run individually.
Co-authored-by: Adam Turner <9087854+aa-turner@users.noreply.github.com>
The new ``python_display_short_literal_types`` configuration option
for the ``py`` domain controls display of PEP 586 ``Literal`` types.
The 'short' format is inspired by PEP 604, using the bitwise OR operator
to distinguish the possible legal values for the argument.
If pygments fails to lex a source string as the specified highlight
language, Sphinx prints a warning. Previously, that warning did not
include the actual source text, although it does include location
information.
However, in some cases the location information may be missing, there
may be multiple highlighted literals on the same line, or the rST is
automatically generated somehow. In such cases, it can be difficult
to determine the source text that led to the error.
With this change, the source text is included in the warning.
Previously, ``nested_parse_with_titles`` always passed ``0`` as the input
offset when invoking ``nested_parse``. When parsing the content of a
directive, as is a common use case for ``nested_parse_with_titles``,
this leads to incorrect source file/line number information, as it
does not take into account the directive's ``content_offset``, which is
always non-zero.
This issue affects *all* object descriptions due to GH-10887. It also
affects the ``sphinx.ext.ifconfig`` extension.
The ``py:module`` and ``js:module`` directives employed a workaround for
this issue, by wrapping the calls to ``nested_parse_with_title`` with
``switch_source_input``. That worked, but was more complicated (and
likely less efficient) than necessary.
This commit adds an optional ``content_offset`` parameter to
``nested_parse_with_titles``, and fixes callers to pass the appropriate
content offset when needed.
This commit eliminates the now-unnecessary calls to
``switch_source_input`` and instead specifies the correct ``content_offset``.
Revert b32841e153
to fix parallel search index building
The image-related changes were already reverted in
2a7c40d07f,
but the search index changes also need to be reverted.
It would be nice to support parallel search index building, but the
necessary support for merging the search indices produced by each
process needs to be added first.
Tests for Sphinx's CLIs, like test_apidoc, indirectly init_console to
initialize translations for Sphinx's console domain, the one with
Sphinx's log messages. This bleeds over subsequent tests by making
warnings translated. Fix this by skipping init_console when running
Sphinx's test suite.
* Fix#11095 (PDF wrong placement of shadow of topic boxes since 5.1.0)
* Fix#11096 (LaTeX shadowsize regression at 5.1.0)
* Fix#11099 (shadowrule legacy sphinxsetup key vanished at 5.1.0)
* Fix#11101 (LaTeX div.topic_padding of sphinxsetup had wrong name)
* Add some checks that various sphinxsetup keys do not break PDF build
* Update LaTeX docs
* Update CHANGES
* Can not use :dudir:`contents` has it links to wrong place
The link relationship keyword `shortcut` does not appear in the HTML 5 specification [1].
It was used by historic browsers (i.e. Internet Explorer 6) which Sphinx no longer supports.
[1]: HTML5 Specification, 4.6.7.8 Link type "icon", https://html.spec.whatwg.org/#rel-icon
