Message 61432 - Python tracker

➜

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	gvanrossum
Recipients	christian.heimes, georg.brandl, gvanrossum, schmir
Date	2008-01-21.18:16:09
SpamBayes Score	0.0017677555
Marked as misclassified	No
Message-id	<1200939373.28.0.937389605544.issue1881@psf.upfronthosting.co.za>
In-reply-to

Content
I don't know what common stack sizes are any more. Even on the same platform, the main thread may have a different stack size than other threads. Would it make sense to make this limit more platform-dependent? I guess really good would be a way to handle C stack overflows more gracefully, but that's for another era. All said, let's try a 3x increase, and have a unittest that pushes the limits to the max (both a case that is one short of the limit and a case that is over the limit, and is expected to raise an exception).

I don't know what common stack sizes are any more.  Even on the same
platform, the main thread may have a different stack size than other
threads.  

Would it make sense to make this limit more platform-dependent?

I guess really good would be a way to handle C stack overflows more
gracefully, but that's for another era.

All said, let's try a 3x increase, *and* have a unittest that pushes the
limits to the max (both a case that is one short of the limit and a case
that is over the limit, and is expected to raise an exception).

History
Date	User	Action	Args
2008-01-21 18:16:13	gvanrossum	set	spambayes_score: 0.00176776 -> 0.0017677555 recipients: + gvanrossum, georg.brandl, christian.heimes, schmir
2008-01-21 18:16:13	gvanrossum	set	spambayes_score: 0.00176776 -> 0.00176776 messageid: <1200939373.28.0.937389605544.issue1881@psf.upfronthosting.co.za>
2008-01-21 18:16:10	gvanrossum	link	issue1881 messages
2008-01-21 18:16:09	gvanrossum	create