-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Fail with an explicit error on PyPy #20384
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
Conversation
This comment has been minimized.
This comment has been minimized.
|
According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅ |
hauntsaninja
left a comment
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.
Not sure error in setup.py is the best, since PyPy will presumably pull the pure Python wheel. Maybe we should import librt in main at runtime and error if it fails
|
Oh, hm, TBH I don't know how PyPy works, but yeah, that may be more robust. I think we don't even need to try importing |
|
Follow up in #20389 |
Fixes mypyc/librt#21 Fail with an explicit user-friendly error on PyPy.
Fixes mypyc/librt#21
Fail with an explicit user-friendly error on PyPy.