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
specify sphinx
version
#506
Conversation
docutils==0.18 was recently pushed and breaks the same as docutils==0.17
Normally sphinx already limits the version of docutils to < 0.18 (until they officially support it, sphinx-doc/sphinx#9777), in which case I would think we don't need to pin as well. What version of sphinx are you using? And do you have an example of something that breaks? (there might also be specific things in our theme and not just sphinx that is impacted by the new docutils release) |
@jorisvandenbossche When you pip install I will get back to you with a minimal example to reproduce the error. I was using |
It might be that you are (for some other reason) getting an older version of sphinx that does not include those stricter version requirements on sphinx (see also sphinx-doc/sphinx#9777 (comment)) |
@jorisvandenbossche I've confirmed this is a problem with |
It might be interesting to check where this pin for sphinx is coming from. Sphinx actually has a 3.5.4 release that specifically fixed this. |
I'd be in favor of supporting the latest two major releases of Sphinx (and testing against them). I think it's too restrictive if this theme only works with the latest major release |
Instead of pinning Sphinx, why don't we pin docutils to |
@choldgraf That was the original proposal; if you guys decide you want that I can revert the last commit. |
I was going to update this one to pin at 3.5.4 as @jorisvandenbossche mentioned, but the branch seems to be deleted so I opened up #595 |
Superseded by #595, so closing here. |
Problem:
docutils==0.18
was recently pushed and breaks the same asdocutils==0.17
.Solution: Use
docutils<0.17
instead ofdocutils!=0.17.0