-
Notifications
You must be signed in to change notification settings - Fork 14
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
Pydantic >2.0.* seems to result in problems #196
Labels
bug
Something isn't working
Comments
Branch 196-Pydantic-2-0-seems-to-result-in-problems created! |
tstorek
added a commit
that referenced
this issue
Jul 14, 2023
tstorek
added a commit
that referenced
this issue
Jul 14, 2023
tstorek
added a commit
that referenced
this issue
Jul 17, 2023
tstorek
added a commit
that referenced
this issue
Jul 17, 2023
This was referenced Aug 1, 2023
fixed by #199 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When running my code (can't post it here), I get an import error from filip as a site package installed in an venv!
I had to adjust some of the pathes in the error message, due to restricted information!
To Reproduce
Steps to reproduce the behavior:
pip install filip
BaseSettings
from Pydantic (in my case it wasServiceGroup
)Environment (please complete the following information):
Additional context
In
requirements.txt
andsetup.py
the version of pydantic is just defined using>=
which is likely the cause. In pydantic v2.* there seems to be a change in the structure resulting in the ImportError above!Maybe fixing it to
pydantic~=1.10.11
(lastest v1 version) would solve the problem until v2 is more common!At the moment in theory everyone installing filip into a new environment will end up with this error!
The text was updated successfully, but these errors were encountered: