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
v1.9 is coming! #3537
Comments
These two typing issues would be good to resolve before release:
#2650 is a breaking change and should probably be marked as such - custom encoders might not be equipped to handle |
I reckon #3201 and #3182 are important to fix regressions in |
Thanks both. I'll look at these. I meant to close this to use the discussion which is linked from the release #3538. I'll move your comments across. |
My mistake to create this, please use #3538 instead. |
Hi all,
v1.9 is VERY overdue, but we're nearly there.
My plan before release:
v1.9a1
and encourage people to test it before release - I guess I'll give people a week?v1.9a1
on projects where I use pydanticMy aim is to get the new release out this year.
Are there any other PRs you really really want in this release? If so please comment below.
Similarly if you find a bug with this release, please create an issue and link to it here.
The text was updated successfully, but these errors were encountered: