This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tim.peters
Recipients
Date 2006-04-23.20:25:32
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=31435

Right, this one: "a simple shadow of the function as a
module level function".  If it affects all threads (which it
does), then a module function is a natural place for it.  If
I a saw a method on the Thread class, the most natural (to
me ;-)) assumption is that a_thread.stack_size(N) would set
the stack size for the specific thread `a_thread`, but not
affect other threads.  Part of what makes that "the most
natural" assumption is that Thread has no class or static
methods today.  As a module-level function, no such
confusion is sanely possible.

Sticking "stack_size" in threading.__all__, and adding

from thread import stack_size

to threading.py is all I'm looking for here.  Well, plus
docs and a test case ;-)
History
Date User Action Args
2007-08-23 15:47:02adminlinkissue1454481 messages
2007-08-23 15:47:02admincreate