Hi Brett,
On Tue, Jun 27, 2006 at 10:32:08AM -0700, Brett Cannon wrote:
OK, with you and Thomas both wanting to keep it I will let it be. I just
won't worry about fixing it myself during my interpreter hardening crusade.
I agree with this too. If I remember correctly, you even mentioned in
If you look at that crasher, you will notice that recursion depth is set to 1 30 before any code is run. If you remove that setting high setting and go with the default then the test doesn't crash and raises the appropriate RuntimeError.
Setting the recursion depth to such a high number will
On 6/27/06, Brett Cannon [EMAIL PROTECTED] wrote:
If you look at that crasher, you will notice that recursion depth is set to 1 30 before any code is run. If you remove that setting high setting and go with the default then the test doesn't crash and raises the appropriate RuntimeError.
Setting
On 6/27/06, Thomas Wouters [EMAIL PROTECTED] wrote:
On 6/27/06, Brett Cannon
[EMAIL PROTECTED] wrote:
If you look at that crasher, you will notice that recursion depth is set to 1 30 before any code is run. If you remove that setting high setting and go with the default then the test doesn't
Brett Cannon [EMAIL PROTECTED] writes:
If you look at that crasher, you will notice that recursion depth is set
to 1 30 before any code is run. If you remove that setting high
setting and go with the default then the test doesn't crash and raises the
appropriate RuntimeError.
Setting the
On 6/27/06, Michael Hudson [EMAIL PROTECTED] wrote:
Brett Cannon [EMAIL PROTECTED] writes: If you look at that crasher, you will notice that recursion depth is set to 1 30 before any code is run.If you remove that setting high
setting and go with the default then the test doesn't crash and
