Skip to content

Conversation

@flying-sheep
Copy link
Contributor

@flying-sheep flying-sheep commented Nov 20, 2025

Purpose

Since the MRPV is 3.11, we can just use the BaseExceptionGroup class as base class for the ImportExceptionGroup, which will result in much more context being included in the traceback.

This allows people to more easily debug why autosummary fails when it does.

References

@AA-Turner
Copy link
Member

@flying-sheep thanks for the PR! Tests are failing, please can you also add a changed entry?

A

@flying-sheep
Copy link
Contributor Author

flying-sheep commented Nov 21, 2025

All done! I’m excited, this was one of my first big usability issues with Sphinx, and soon it’ll be gone forever!

@flying-sheep flying-sheep changed the title fix: use exception group fix: use exception group for autosummary import errors Nov 21, 2025
@AA-Turner AA-Turner changed the title fix: use exception group for autosummary import errors Use PEP 654 ExceptionGroup for autosummary import errors Nov 24, 2025
@AA-Turner
Copy link
Member

Thanks!

A

@AA-Turner AA-Turner merged commit 0bdfa74 into sphinx-doc:master Nov 24, 2025
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Autosummary import exception message is misleading and missing context

2 participants