-
Notifications
You must be signed in to change notification settings - Fork 403
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
Maintenance: Pydantic v1 end of life #4067
Comments
Thank you for opening this Leandro. I will try to understand the impact this might have on the Bedrock Agents resolver, including timelines. |
This is really messing up my development. I use Pydantic elsewhere in my codebase for direct model validation and I'd like to use a non EOL version of Pydantic but I can't because I have to satisfy the ^1.8.2 pin in the metadata (pyproject.toml) of Powertools. Please prioritize this. Pydantic is already on 2.8. |
@medley56 Hi there, current versions of Powertools are compatible with Pydantic v2. There’s a note in the docs on how to do this https://docs.powertools.aws.dev/lambda/python/latest/utilities/parser/#using-pydantic-v2 |
We are working to release Powertools v3 soon (hopefully in August) and in this new major release we are removing Pydantic v1. |
We are working on the RFC for Powertools V3. Check more information here: #4189 |
|
Why is this needed?
Pydantic plays a critical role in Powertools, working as a key dependency across various utilities. While Powertools is fully compatible with Pydantic v2, the default version remains Pydantic v1. The active development of Pydantic v1 ceased with the launch of v2.
Although Pydantic v1 continues to address bug fixes and security problems, development will come to a definitive halt, including security updates, as of 30/06/2024.
I'm opening this issue to keep it on our radar and initiate a discussion about definitively dropping support for Pydantic v1.
https://docs.pydantic.dev/latest/version-policy/#pydantic-v1
Which area does this relate to?
Parser
Solution
No response
Acknowledgment
The text was updated successfully, but these errors were encountered: