Skip to content
New issue

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

Fix sphinx-doc#9322: KeyError is raised on PropagateDescDomain transform #9334

Merged

Conversation

tk0miya
Copy link
Member

@tk0miya tk0miya commented Jun 13, 2021

Feature or Bugfix

  • Bugfix

Purpose

PropageteDescDomain applies the domain name from the "domain" attribute
of parent node (desc node) to the desc_signature node.  The structure
has longly generated by ObjectDescription.  But it must not be a new
rule.

This allows to build document that contains non standard doctree.
@tk0miya tk0miya added this to the 4.0.3 milestone Jun 13, 2021
@tk0miya tk0miya changed the title 9322 key error from propagete desc domain Fix sphinx-doc#9322: KeyError is raised on PropagateDescDomain transform Jun 13, 2021
Copy link

@bneradt bneradt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I verified this patch address the Traffic Server doc build issue (#9322). I reproduced #9322 locally with Sphinx==4.0.2 and Python 3.8.3. The KeyError for domain was raised. I then applied this patch locally and rebuilt the ATS docs. The docs build succeeded.

Thank you for turning a patch around so quickly.

@tk0miya tk0miya merged commit 723ad78 into sphinx-doc:4.0.x Jun 29, 2021
@tk0miya
Copy link
Member Author

tk0miya commented Jun 29, 2021

Thank you for your confirmation :-) Just merged.

@tk0miya tk0miya deleted the 9322_KeyError_from_PropageteDescDomain branch June 29, 2021 15:07
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants