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

fix: remove pydantic #189

Merged
merged 8 commits into from
Jul 10, 2023
Merged

Conversation

lp9052
Copy link
Contributor

@lp9052 lp9052 commented Jun 30, 2023

testing migrate to pydantic 2.0

where pydantic_settings is seperate package see #187

I quickly changed everything to pedantic_settings. But Solara depends on vaex which still error out.

I think for now we shall cap pedantic version. @maartenbreddels

@maartenbreddels
Copy link
Contributor

Ok, this is not as simple as I hoped, see pydantic/pydantic#6497

Let's try to get of pydantic. We simply need an easy way to configure things, it shouldn't cause installation issues or breakage.

@maartenbreddels maartenbreddels changed the title testing migrate to pydantic 2.0 fix: remove pydantic Jul 10, 2023
lp9052 and others added 8 commits July 10, 2023 13:57
where pydantic_settings is seperate package
We only use pydantic for the settings, and it is not worth the
dependency. We made the API quite similar, but it is only for internal
use.

We cannot keep using pydantic because v2 does not include pydantic
settings code and needs the pydantic-settings dependency.
However, adding that dependency indirectly requires pydantic v2.
@maartenbreddels maartenbreddels marked this pull request as ready for review July 10, 2023 12:40
@maartenbreddels
Copy link
Contributor

Thanks for starting this. In the end, we had to remove Pydantic, otherwise we'd have to choose between v1 and v2 and we don't want to do that for our users.

@maartenbreddels maartenbreddels merged commit ab21337 into widgetti:master Jul 10, 2023
@lp9052
Copy link
Contributor Author

lp9052 commented Jul 11, 2023

Sorry for the delay, I was preparing my PhD application. It's unfortunate that we have to adopt this internally. Their decision to make a big change in a popular package is baffling. It's basically ineffective until everyone switches to pydantic2. I was dinged about our failing builds this morning, so I'm glad this was addressed. I truly appreciate it.

@lp9052 lp9052 deleted the migrate_to_pydantic_2.0 branch July 11, 2023 02:05
@rht
Copy link

rht commented Jul 12, 2023

Thank you for shipping this!

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

Successfully merging this pull request may close these issues.

3 participants