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
bpo-45735: Promise the long-time truth that args=list
works
#30982
Conversation
@rhettinger, you closed your old PR on this without leaving a clue as to why. If you object to documenting this now, please say so. |
OK, I am going to submit the relevant code on this PR (Previously, I plan to open a new PR for |
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
args=list
works
Cleaner English here. Co-authored-by: Tim Peters <tim.peters@gmail.com>
Cleaner English to describe *args*. Co-authored-by: Tim Peters <tim.peters@gmail.com>
I have made the requested changes; please review again |
Thanks for making the requested changes! @tim-one: please review the changes made to this pull request. |
For threads, and for multiprocessing, it's always been the case that ``args=list`` works fine when passed to ``Process()`` or ``Thread()``, and such code is common in the wild. But, according to the docs, only a tuple can be used. This brings the docs into synch with reality. Doc changes by Charlie Zhao. Co-authored-by: Tim Peters <tim.peters@gmail.com>
The added test leaks threads running in the background: I wrote #92885 to fix this issue. |
Thank you, Victor! |
1 similar comment
Thank you, Victor! |
Change description of
threading.Thread
to explain the validity of list args.Add doc example and test cases for
threading.Thread
.https://bugs.python.org/issue45735