[issue24952] stack_size([size]) is actually stack_size(size=0)

2015-08-30 Thread mattip
mattip added the comment: Add the default value 0 to the documentation, please review this patch and not the previous one -- versions: -Python 3.4, Python 3.5, Python 3.6 Added file: http://bugs.python.org/file40304/stack_size.patch ___ Python

[issue24952] stack_size([size]) is actually stack_size(size=0)

2015-08-30 Thread mattip
mattip added the comment: Add default value of 0 to documentation for 2.7 -- versions: +Python 3.5 -Python 2.7 Added file: http://bugs.python.org/file40305/stack_size2.7.patch ___ Python tracker rep...@bugs.python.org

[issue24952] stack_size([size]) is actually stack_size(size=0)

2015-08-28 Thread mattip
mattip added the comment: Add a patch for 2.7 -- versions: +Python 2.7 -Python 3.5 Added file: http://bugs.python.org/file40282/stack_size2.7.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24952

[issue24952] stack_size([size]) is actually stack_size(size=0)

2015-08-28 Thread mattip
New submission from mattip: 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 -- assignee: docs@python components: Documentation files: stack_size.patch keywords: patch messages: 249280

[issue24952] stack_size([size]) is actually stack_size(size=0)

2015-08-28 Thread Martin Panter
Martin Panter added the comment: 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