-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
KeyError: '__main__.Model1:95063711754448'
#9319
Comments
Hmph, definitely a bug. Thanks for the report. Will attempt to fix for 2.7.2 |
The Pydantic version we used before has an issue in the mypy plugin which can lead to actual typing errors slipping through, see pydantic/pydantic#9008. Note that the version we udpate to has this issue: pydantic/pydantic#9319 However, since a workaround is available, we still udpate to avoid introducing new typing errors. Also fix newly found issues. Apparently, polyfactory now has issues with handling field aliases, so we switch to validation aliases, which are sufficient in this case. CMK-17006 Change-Id: I8b8ebb072f0c68b799d28c132c5f5605232db9c7
@jherbel We have a similar problem but we are not using Sequence, I'm wondering if you have any hints on what is the issue here and how to develop a workaround for specific code base? |
Hi @cielecki, by chance, I discovered yesterday that |
@jherbel thanks I decided to go with just going with "Any" in few places in order to make it work in the short term ... |
Hi folks, when did this issue crop up for you? |
Looks like this was introduced in the 2.6.0 release - moving to the 2.8 milestone - still a priority, but going to focus on the 2.7 patch this week. Will send updates soon! |
I cannot really say, sry. We are currently 2.5.2, which is not affected by this. |
Initial Checks
Description
The code below crashes with the following traceback. See also #8897, which was closed.
Example Code
Python, Pydantic & OS Version
The text was updated successfully, but these errors were encountered: