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
docutils 0.20 cannot be used with Sphinx 7.0.0 #11414
Comments
Please would you explain your requirements here? Sphinx specifies the versions of Docutils that it works with to avoid breakage on a new Docutils version. Why do you want to explicitly install Docutils 0.20? A |
Good question. I guess there isn't any current problem I am trying to solve, but rather trying to avoid potential future problems that typically arise when packages cap newer versions of dependencies. I can see two potential problems:
As the author of a downstream package I would like my dependencies to never set caps of versions of dependencies upstream because I cannot do anything about it. Lets say there wasn't an upper cap, and it turns out that Sphinx doesn't work with the new version of docutils, then I could block it for my users in Are you sure that docutils 0.20 doesn't work with Sphinx 7.0.0? Perhaps this is something I could test? |
This question wasn't directed to me, but I'd still like to answer it:
Apparently it would work fine if there wasn't an upper version bound: #11411. About 2 years ago there was a fad in the Python community to add upper version bounds everywhere. Most project have stopped doing that by now, maybe Sphinx should also stop that? Anyway, it looks like we'll be able to use |
I've released Sphinx 7.0.1 which declares support in the project metadata for Docutils 0.20 (as @mgeier pointed out, there is no technical restriction on using Sphinx 7.0.0 with Docutils 0.20). A |
Thanks for the fix and the extra release! |
Describe the bug
When trying to use the latest version of docutils together with Sphinx 7.0.0 I get the following error:
How to Reproduce
In requirements.txt:
Environment Information
Sphinx extensions
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: