fix: deprecation warning from sphinx regarding tuple interface #247
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
|
Thanks for your PR. I will release a new version for v1. |
|
@all-contributors please add @exs-dwoodward for code |
|
I've put up a pull request to add @exs-dwoodward! 🎉 |
|
@exs-dwoodward v1.9.1 is released on pypi. |
|
Thanks @mansenfranzen ! Much appreciated! |
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.
Hi! I wanted to use
autodoc_pydanticwith pydantic v1, but was receiving some DeprecationWarning's specifically from these particular lines.This is already fixed in
mainI see, but for not v1 ofautodoc_pydantic. Would you consider merging this PR to avoid the deprecation warnings when using pydantic v1 still?Thanks! If there is any other formalities that are required for this repo, let me know!