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 skip.montanaro
Recipients gvanrossum, ncoghlan, skip.montanaro, vstinner, yselivanov
Date 2015-06-01.12:20:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CANc-5UxfA0QM_dDz_NaqJxc5L=SqHhJRbrxQHTpSHeTT7turRw@mail.gmail.com>
In-reply-to <1433124694.62.0.501554700121.issue24342@psf.upfronthosting.co.za>
Content
On Sun, May 31, 2015 at 9:11 PM, Yury Selivanov <report@bugs.python.org> wrote:
> Current python will crash with a "RuntimeError: maximum recursion depth exceeded" ...

If it's good enough for other programmer-induced infinite recursion
(and in my experience the cause is generally quite obvious from the
traceback), why wouldn't it be good enough in this case?
History
Date User Action Args
2015-06-01 12:20:16skip.montanarosetrecipients: + skip.montanaro, gvanrossum, ncoghlan, vstinner, yselivanov
2015-06-01 12:20:16skip.montanarolinkissue24342 messages
2015-06-01 12:20:16skip.montanarocreate