-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
threading: ExceptHookArgs funkiness #4767
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
Comments
What I a useful comment I left there. The stubs try to follow the implementation (starting here) and I guess I wanted to express my consternation about the weird renaming going on there. That said, I don't think the stubs are accurate. (In case What we should probably do:
|
The previous typing meant `threading.ExceptHookArgs` could not be used to type a value. The new typing follows what cpython does in the happy path (`_thread` exists rather than the pure-python fallback being used). Fixes python#4767.
The previous typing meant `threading.ExceptHookArgs` could not be used to type a value. The new typing follows what cpython does in the happy path (`_thread` exists rather than the pure-python fallback being used). Fixes python#4767.
The previous typing meant `threading.ExceptHookArgs` could not be used to type a value. The new typing follows what cpython does in the happy path (`_thread` exists rather than the pure-python fallback being used). Fixes #4767.
The
threading.excepthook
variable (added in Python 3.8) accepts athreading.ExceptHookArgs
argument (available at runtime). The typing around it in typeshed is not straightforward:typeshed/stdlib/2and3/threading.pyi
Lines 157 to 164 in 8c20938
Sorry but I guess I have to ask 😀
The
_thread
part is:typeshed/stdlib/3/_thread.pyi
Lines 30 to 38 in 8c20938
My practical issue is that this:
results in
The text was updated successfully, but these errors were encountered: