Skip to content
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

Closed
2 of 4 tasks
samuelcolvin opened this issue Dec 18, 2021 · 4 comments
Closed
2 of 4 tasks

v1.9 is coming! #3537

samuelcolvin opened this issue Dec 18, 2021 · 4 comments
Labels

Comments

@samuelcolvin
Copy link
Member

samuelcolvin commented Dec 18, 2021

Hi all,

v1.9 is VERY overdue, but we're nearly there.

My plan before release:

  • merge any open PRs with the "ready for review" label - currently there are 3, all basically ready to merge
  • create a pre-release v1.9a1 and encourage people to test it before release - I guess I'll give people a week?
  • test v1.9a1 on projects where I use pydantic
  • release v1.9

My 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.

@layday
Copy link
Contributor

layday commented Dec 19, 2021

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 BaseModels.

@PrettyWood
Copy link
Member

PrettyWood commented Dec 19, 2021

I reckon #3201 and #3182 are important to fix regressions in master/main.
The PR on dataclasses could be very nice too since it fixes a lot of issues. I'll see what I can do on Monday or Tuesday.
Computed fields can and should definitely wait for v1.10: it's a big and impactful change that cannot be rushed and needs perf tests

@samuelcolvin
Copy link
Member Author

samuelcolvin commented Dec 19, 2021

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.

@pydantic pydantic locked as off-topic and limited conversation to collaborators Dec 19, 2021
@samuelcolvin
Copy link
Member Author

My mistake to create this, please use #3538 instead.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants