-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[docs] Update sphinx to 3.5.4 #61601
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
Conversation
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit ea56322 (more details on the Dr. CI page):
ci.pytorch.org: 1 failedThis comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions to the (internal) Dr. CI Users group. |
|
@albanD I can haz approval + import plz? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@albanD has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
|
@albanD has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
|
@albanD can you please merge this? |
|
Hey! |
|
Rebased |
|
Ho we see the same failures here now :D So that was a valid race of something that landed in the meantime? |
Sphinx 4.x is out, but it seems that requires many more changes to adopt. So instead use the latest version of 3.x, which includes several nice features. * Add some noindex directives to deal with warnings that would otherwise be triggered by this change due to conflicts between the docstrings declaring a function and the autodoc extension declaring the same function. * Update distributions.utils.lazy_property and related code to make it look like a regular property when sphinx autodoc inspects classes.
|
Reproduced the failures locally, fixed them, and pushed a new version. |
|
@albanD has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
|
Awesome! |
|
@garymm while looking closer at the final doc, there are some un-expected spacing in the function definitions. With a lot of extra spacing and in particular between the nn and the Conv2d. Do you think we can fix that? |
|
I see what you mean. I guess there's something that can be changed in the theme CSS, but I really have no experience with CSS. In the mean time I'll take a look to see if I can figure it out on my own. If we need to revert, let me know and I will revert just the requirements.txt change and leave the other parts of this PR. |
|
For ref, I opened an issue about this a while ago: pytorch/pytorch_sphinx_theme#115 |
|
@garymm I would love to be able to keep this new version in. I think it is ok for the master doc to not look optimal for a few days while we investigate this. |
|
Trying to fix this in pytorch/pytorch_sphinx_theme#134 |


Sphinx 4.x is out, but it seems that requires many more changes to
adopt. So instead use the latest version of 3.x, which includes
several nice features.
be triggered by this change due to conflicts between the docstrings
declaring a function and the autodoc extension declaring the
same function.
regular property when sphinx autodoc inspects classes.