-
Notifications
You must be signed in to change notification settings - Fork 141
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
fix: remove pydantic #189
Conversation
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. |
1cc2b94
to
38a10ea
Compare
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.
a49f089
to
c898080
Compare
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. |
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. |
Thank you for shipping this! |
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