-
Notifications
You must be signed in to change notification settings - Fork 2
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
Cannot find component ProtocolIntersection\u200b
#4
Comments
Hmmm... I'm sometimes seeing this error now even when everything is contained in a single file without importing |
ProtocolIntersection
ProtocolIntersection\u200b
This gist seems sufficient to reproduce the error for me after it has been run a couple of times to generate a |
Hey. Thanks for reporting! Just wanted to mention that life's hectic, so I might take a few days to look at this issue in depth. Should you have any ideas before I investigate, shoot. |
I have no solution so far. Frankly I didn't have time to dive deep, I only scratched a surface. If mypyc/mypyc#973 gets fixed, we can return to the old implementation that didn't add artificial suffixes to the class names. I'm happy to consider any alternative approaches to the implementation anyone might have. |
If one module imports
ProtocolIntersection
, and then another module attempts to import it from that module,mypy
seems unable to lookupProtocolIntersection
in the imported module's namespace (maybe due to the presence of a zero-width space at the end?):Also note that reproduction here is a bit tricky, since it seems to depend on the current status of
.mypy_cache
, though it always shows up for me after runningmypy
enough times. I'm on Python 3.9 andmypy
1.2.0.mypy.ini
is just:The text was updated successfully, but these errors were encountered: