➜

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 terry.reedy
Recipients Trundle, loewis, marienz, terry.reedy
Date 2011-03-04.21:30:09
SpamBayes Score 6.6565167e-09
Marked as misclassified No
Message-id <1299274211.29.0.177006727238.issue11343@psf.upfronthosting.co.za>
In-reply-to
Content 
I agree that compile-time stack exhaustion is different from runtime object-heap exhaustion and could/should have a different error.

I agree with Martin (from 2000) that SyntaxError is not right either. Perhaps a new ParseError subclass thereof. I believe IndentationError was added since 2000. Its doc is "Base class for syntax errors related to incorrect indentation." and it has TabError as a subclass, so its use for too many indents (not really 'incorrect') is not obvious. But having the position marked (if it would be) would be a plus.

I presume REPL == read-eval-print-loop (from Google). Would a new error help such programs (like code.interact, or IDLE)?
History
Date User Action Args
2011-03-04 21:30:11terry.reedysetrecipients: + terry.reedy, loewis, marienz, Trundle
2011-03-04 21:30:11terry.reedysetmessageid: <1299274211.29.0.177006727238.issue11343@psf.upfronthosting.co.za>
2011-03-04 21:30:10terry.reedylinkissue11343 messages
2011-03-04 21:30:09terry.reedycreate