-
Notifications
You must be signed in to change notification settings - Fork 324
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
Compatibility with Pydantic 2.10 #369
Comments
I think the easiest solution would be to clean up the contents of the |
The example code in the docs is also broken because of pydantic 2.10. Downgrading to 2.9.2 makes it work again |
I have managed to not throw any errors but its not rendering anything anymore will try to figure out a nice solution |
Finished the refactor and have working version of FastUI added a PR so maybe we can get someone from pydantic to look at it in near future. |
Due to a circular import, the
AnyComponent
alias is imported in anif TYPE_CHECKING:
block infastui.components.forms
:FastUI/src/python-fastui/fastui/components/forms.py
Lines 12 to 13 in 5d9d604
and later used in one of the defined models for this module:
FastUI/src/python-fastui/fastui/components/forms.py
Lines 187 to 191 in 5d9d604
While this used to work in <2.10 because of namespace pollution inconsistencies, it doesn't with 2.10 as
AnyComponent
(which doesn't exist in the module namespace at runtime) isn't available.Best way forward would be to fix the circular import, haven't found a viable implementation yet.
The text was updated successfully, but these errors were encountered: