-
Notifications
You must be signed in to change notification settings - Fork 323
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
MAINT: Work around Sphinx deprecation #301
Conversation
Thanks for looking into this I wonder if we could remove it entirely, since the sphinx |
It indeed seems to be deprecated in a PR (sphinx-doc/sphinx#7264) that removed support for docutils 0.13 and 0.14 |
It looks like that will be true for Sphinx 4, but I'm not sure when that will actually land (they say Spring at least) and when it will be adopted by people. It looks like it is still called in the 3.x maintenance branch. Given the tentativeness of the release date and how slow people will be to upgrade sphinx once 4 comes out, seems worthwhile to me to keep some code in for backward compat. I could add something instead like |
With "removing entirely", I mean only the |
Done. I used |
Yeah, the distutils deprecation is something we are going to handle in many places (many projects use |
Thanks! |
Not 100% sure if this is a correct workaround for this deprecation:
But it seems to work locally at least.