-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 typing of multiprocessing.Value and Array #11576
Conversation
could fix python#8799 and python#9898, but request review for side effects. Without this change, static type checkers would treat `Value(ctypes.c_float, 0.0)` like `ctypes.c_float`, but `Value` offers a field `value` for storage
This comment has been minimized.
This comment has been minimized.
According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉 |
I do not want to be too demanding, but just to be sure I'm not missing anything: Is there anything left for me to help going forward to merge? |
One of the maintainers will hopefully find time to look at this soon. |
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.
My experience with ctypes and multiprocessing is limited, but based on the lack of complaints from our tests, the review by @f0rmiga, and playing around with ctypes a bit, this change makes sense to me.
could fix #8799 and #9898, but request review for side effects. Without this change, static type checkers would treat
Value(ctypes.c_float, 0.0)
likectypes.c_float
, butValue
offers a fieldvalue
for storage