-
Notifications
You must be signed in to change notification settings - Fork 5
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 the build by bumping to crate-docs 1.0.0 #246
Conversation
I actually don't know why "#make-changes" isn't working anymore. The browser still honors and evaluates this anchor perfectly. We will probably have to file an issue with Sphinx on this.
@amotl can you bring in my changes to I'm happy to then merge this pr and drop the related commit from #245 |
side note: I am not clear on how this fixes crate/crate-docs#65. or rather, I am not clear on what causes crate/crate-docs#65. can you elaborate? |
I believe the reason is that crate-docs 0.4.0 explicitly tests for python3.7? However, I don't know exactly. I have been able to reproduce it on my machine and bumping to crate-docs 1.0.0 mitigated the problem. So, let's just go ahead, right? |
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.
I think it's a bit unconventional to do the Makefile change in a separate pr (#247) but the end result will be the same so I don't mind. let's go ahead
.. _developer guide: https://github.com/crate/crate-docs-theme/blob/master/DEVELOP.rst#make-changes | ||
.. _developer guide: https://github.com/crate/crate-docs-theme/blob/master/DEVELOP.rst#user-content-make-changes |
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.
Attaching to this, I just created sphinx-doc/sphinx#9016.
Hi there,
this patch fixes crate/crate-docs#65 reported by @msbt. You can either choose this one, or bring in #245 instead. Or do both, one after the other.
With kind regards,
Andreas.