Switch to Pydantic v1 namespace and allow Pydantic v1 or v2 #168
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.
What I am changing
This change incorporates the use of the Pydantic v1 namespace which was introduced in Pydantic 1.10.17 and all 2.x versions. This allows the use of Pydantic v1 while also supporting either Pydantic >=1.10.17,<3. The goal being to allow users of this package a planned upgrade path to Pydantic 2.x instead of an abrupt switch.
See #166 for more on this issue
How I did it
v1
namespace (e.g.from pydantic.v1 import ...
)How you can test it
Reference
See the Pydantic migration guide which was updated to reference the new v1 namespace support back in August: https://docs.pydantic.dev/latest/migration/#continue-using-pydantic-v1-features