You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Numpydoc experienced test-suite failures in a mocked sphinx-app due to missing a private _exception_on_warning attribute. This started happening with sphinx 8.1 and is likely related to #12743.
Generally speaking, I don't think this is a problem with sphinx just a change in the underlying logic related to warningiserror and _exception_on_warning. It's likely the behavior change is intentional - in that case please close this. I just thought I'd raise it in case this is unexpected.
The fix in numpydoc is to explicitly add the _exception_on_warning attribute to the mocked sphinx app instance: numpy/numpydoc#586.
Indeed, mocking sphinx.application.Sphinx isn't a supported use-case, so I don't consider this a bug -- but adding the private _exception_on_warning attribute is the correct resolution.
Describe the bug
Numpydoc experienced test-suite failures in a mocked sphinx-app due to missing a private
_exception_on_warning
attribute. This started happening with sphinx 8.1 and is likely related to #12743.Generally speaking, I don't think this is a problem with sphinx just a change in the underlying logic related to
warningiserror
and_exception_on_warning
. It's likely the behavior change is intentional - in that case please close this. I just thought I'd raise it in case this is unexpected.The fix in numpydoc is to explicitly add the
_exception_on_warning
attribute to the mocked sphinx app instance: numpy/numpydoc#586.How to Reproduce
pip install numpydoc[test]==1.8.0 sphinx>=8.1
pytest --pyargs numpydoc
Environment Information
Sphinx extensions
numpydoc
Additional context
No response
The text was updated successfully, but these errors were encountered: