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
7.5.6 Thread Objects is too vague #40019
Comments
Some items which could be improved.... "Once the thread's activity is started, the thread is considered This is a bit silly. Either these attributes are intended to be "If the subclass overrides the constructor, it must make sure to This is misleading. You need to call "Thread.__init__ (self)", i.e. "join([timeout]) ... When the timeout argument is present and not What happens if you pass None? Does it wait forever? Is this any "A thread can be join()ed many times." Presumably only if all but the last call timed out? Or maybe not? |
Logged In: YES Submitted Patch 1107656 which addresses the 'alive' and |
Logged In: YES The second item is no bug. Methods in the docs are always I have addressed the join() issues in Closing as the remaining issue is covered by the patch |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: