Work around docutils v0.21.2 deprecation issue #62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* A deprecation warning in docutils surfaces through sphinx-autodoc-typehints. A workaround was submitted to sphinx-autodoc-typehints but that workaround/fix is not yet in a release version. More background info can be found here tox-dev/sphinx-autodoc-typehints#454
|
I'm like a monkey with a hand grenade. Closing this PR. I think this change needs to happen in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
'autodoc-process-docstring' threw an exception (exception: The frontend.OptionParser class will be replaced by a subclass of argparse.ArgumentParser in Docutils 0.21 or later.) tox-dev/sphinx-autodoc-typehints#454
Maybe this PR will trigger some pip deps lock file magic, magic I'll have to do it in the CI. Gotta start somewhere.