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
stack_size([size]) is actually stack_size(size=0) #69140
Comments
when using thread.stack_size or threading.stack_size, if no argument is provided the stack size is reset to default. Trivial patch for 3.5 provided |
Add a patch for 2.7 |
In my mind this notation implies the folowing should work: >>> threading.stack_size(size=0)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: stack_size() takes no keyword arguments Perhaps you really just want make it more explicit that the special value 0 is used by default if the argument omitted? See also bpo-8706 about supporting named keyword parameters, and bpo-13386 and bpo-23738 about other possible notations to document the default value. |
Add the default value 0 to the documentation, please review this patch and not the previous one |
Add default value of 0 to documentation for 2.7 |
This version looks okay. I’ll commit it when I get a chance. BTW, there’s no point changing the version for each patch. The version field only applies to the whole bug report. |
New changeset 328383905eaf by Martin Panter <vadmium> in branch '3.4': New changeset 606082fa2804 by Martin Panter <vadmium> in branch '3.5': New changeset 501c9ab07996 by Martin Panter <vadmium> in branch 'default': New changeset 79afd50396c5 by Martin Panter <vadmium> in branch '2.7': |
Thanks for the patches |
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: