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 Ramchandra Apte, benjamin.peterson, georg.brandl, roger.serwy, terry.reedy
Date 2011-12-24.03:28:49
SpamBayes Score 4.024347e-07
Marked as misclassified No
Message-id <1324697330.68.0.803919211839.issue13644@psf.upfronthosting.co.za>
In-reply-to
Content
When I run this with 3.2.2 IDLE, from an edit window, I get an MSVC++ Runtime Library window: "Runtime Error! .../pythonw This application has requested termination in an unusual way...". When I close that, IDLE continues. So I would say that this is not a crash and not even a bug, but a particular choice of undefined behavior given infinite loop code. So we have no obligation to change it. I presume the change from 2.x is a side-effect of a change to improve something else.

def recurse(): recurse()
recurse()

does print "RuntimeError: maximum recursion depth exceeded" but only after printing a    l  o  n  g    traceback. So for running from IDLE, I at least half prefer the immediate error box with no traceback.
History
Date User Action Args
2011-12-24 03:28:50terry.reedysetrecipients: + terry.reedy, georg.brandl, benjamin.peterson, roger.serwy, Ramchandra Apte
2011-12-24 03:28:50terry.reedysetmessageid: <1324697330.68.0.803919211839.issue13644@psf.upfronthosting.co.za>
2011-12-24 03:28:50terry.reedylinkissue13644 messages
2011-12-24 03:28:49terry.reedycreate