check for existing roles/directives when registering new ones from an extension #1962
Milestone
Comments
t4ngo
added a commit
to t4ngo/sphinxcontrib-traceables
that referenced
this issue
May 29, 2016
Sphinx added checking for registering nodes, roles, and directives which are already registered (see commit sphinx-doc/sphinx@cdf0f82 and sphinx-doc/sphinx#1962). That breaks the testing logic of sphinx-testing (see https://github.com/sphinx-doc/sphinx-testing) where subsequent tests cause reregistration warnings. This change adds a local, slightly modified, version of Sphinx' built-in testing utilities. Resolves #3.
t4ngo
added a commit
to t4ngo/sphinxcontrib-multilatex
that referenced
this issue
Jun 6, 2016
Sphinx added checking for registering nodes, roles, and directives which are already registered (see commit sphinx-doc/sphinx@cdf0f82 and sphinx-doc/sphinx#1962). That breaks the testing logic of sphinx-testing (see https://github.com/sphinx-doc/sphinx-testing) where subsequent tests cause reregistration warnings. This change adds a local, slightly modified, version of Sphinx' built-in testing utilities.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From Peter Eastman on sphinx-users:
"""
It turns out Sphinx 1.3 introduced a new role called "numref", which is the same name the extension was using. It then silently ignored the extension and created instances of its own node type rather than the extension's type.
Glad to have that figured out. Could I make a feature request, though? If an extension defines a role or directive with the same name as a built in one, could it produce an error rather than silently ignoring it? That would have saved me hours of debugging.
"""
The text was updated successfully, but these errors were encountered: