-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: annoying mypy error is annoying #26581
Conversation
Size Change: 0 B Total Size: 1.11 MB ℹ️ View Unchanged
|
downgrading to
means no more errors running mypy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Low context but makes sense
ok, this is silly. mypy results are apparently bouncing but 🤷 going to binary search in commits using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where did this go? 🤯
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i really like mypy, this is all very straight-forward and enjoyable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
completely tore down my environment, and still get this result 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't get the error today, but i've installed so many different versions of mypy and associated deps that i don't trust my machine
lately I get an error when running mypy
i'm not the only one: https://posthog.slack.com/archives/C0113360FFV/p1733155706603479
AssertionError: Cannot find component 'trace' for 'opentelemetry.trace'
on updating to latest mypy I then get
OverflowError: int too big to convert
We can fix this by not writing to a mypy cache. Since that's what's failing
This is a workaround not a fix 🙈
Regardless of how I try to ignore it the last output we see in verbose mode is something like
if I delete the
py.typed
file in the mimesis package then we no longer get the error but things likein the mypy.ini didn't change anything
presumably mimesis has a very large number in it (or something that resolve to one) and when mypy tries to cache it the json serializer can't cope 🤷
i tried updating to mimesis v18 which didn't affect anything - and is a 13 major version jump so I didn't include it here
it isn't clear to me if this is a bug in mypy or mimesis or the overlap between them (or indeed something else 🙈)